← previous blocknext block →recent activity
Analyzing
Block #94,475,410
14 transactions · 9 stateful · 2026-08-09 11:18:55 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,475,410 · 14 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
6w08w19w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdd67ca0d…08e5
0x34b655…2a6f
4 touches
1 conflict
0xdd67ca0d…08e6
0x34b655…2a6f
4 touches
1 conflict
0x4c6d6bb7…e83f
0x065c9d…c394
4 touches
1 conflict
0xe3d22957…64ea
0x34b655…2a6f
4 touches
1 conflict
0x9a74c40b…6f78
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity