← previous blocknext block →recent activity
Analyzing
Block #94,196,650
14 transactions · 9 stateful · 2026-08-08 11:44:07 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,196,650 · 14 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
1w05w06w19w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af644dc…0822
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x7ee74e97…55f1
0x34b655…2a6f
4 touches
1 conflict
0x859c92cc…430b
0x34b655…2a6f
4 touches
1 conflict
0x8fa97406…a574
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc4467b40…f5b2
0x34b655…2a6f
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
1 conflict on slot 0x1af644dc54…000822
Audit this contract →
← previous block·next block →recent activity