← previous blocknext block →recent activity
Analyzing
Block #94,794,712
16 transactions · 16 stateful · 2026-08-10 14:06:24 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,794,712 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w07w18w29w110w313w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a66856f…8b9f
0x34b655…2a6f
6 touches
3 conflicts
0x6847107a…f468
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd3ef514b…f35f
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2491d756…b71c
0xa6afd3…d132
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 0x7a66856fea…6a8b9f
Audit this contract →
← previous block·next block →recent activity