← previous blocknext block →recent activity
Analyzing
Block #94,484,333
9 transactions · 8 stateful · 2026-08-09 12:03:48 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,484,333 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61d37f4f…61d2
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xaeb4008e…298d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1d0a04dd…b892
0x34b655…2a6f
2 touches
0 conflicts
0x31ba5616…4601
0x34b655…2a6f
2 touches
0 conflicts
0x32d8a305…96ee
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x61d37f4fd4…e161d2
Audit this contract →
← previous block·next block →recent activity