← previous blocknext block →recent activity
Analyzing
Block #94,236,172
16 transactions · 16 stateful · 2026-08-08 15:04:25 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,236,172 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w09w110w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53699236…fede
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x51804339…c476
0x065c9d…c394
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x8b41ec8f…c2da
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0x53699236c4…57fede
Audit this contract →
← previous block·next block →recent activity