← previous blocknext block →recent activity

Analyzing

Block #94,288,475

24 transactions · 24 stateful · 2026-08-08 19:29:28 UTC

Parallelism

50/100

Blocked

63%

Avg conflicts / tx

2.21

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #94,288,475  ·  24 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x734ee320…caae

0x34b655…2a6f

12 touches
15 conflicts

0x5502e1cc…3910

0x34b655…2a6f

10 touches
10 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

10 touches
10 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x58d0a23c…5d3a

0x34b655…2a6f

8 touches
6 conflicts

0x401a563c…0ae7

0x34b655…2a6f

6 touches
3 conflicts

0x2a6ce996…6902

0x34b655…2a6f

6 touches
3 conflicts

0x17c3727d…cb0e

0x34b655…2a6f

6 touches
3 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Perpl

15 conflicts on slot 0x734ee32053…cecaae

← previous block·next block →recent activity