← previous blocknext block →recent activity
Analyzing
Block #94,371,806
9 transactions · 7 stateful · 2026-08-09 02:32:54 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,371,806 · 9 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
2w03w15w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b64d0d7…af06
0x34b655…2a6f
4 touches
1 conflict
0x349f436e…80e6
0x34b655…2a6f
4 touches
1 conflict
0x8565e674…eaf1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd22dd5e8…83ff
0x34b655…2a6f
4 touches
1 conflict
0xe4c602c1…04be
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 0x2b64d0d7f5…78af06
Audit this contract →
← previous block·next block →recent activity