← previous blocknext block →recent activity
Analyzing
Block #94,816,826
24 transactions · 18 stateful · 2026-08-10 15:57:38 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,816,826 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w010w111w217w018w121w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0x6700a122…8702
0x968279…9342
4 touches
1 conflict
0x6700a122…86fb
0x968279…9342
4 touches
1 conflict
0x6700a122…86fc
0x968279…9342
4 touches
1 conflict
0x6700a122…86ff
0x968279…9342
4 touches
1 conflict
0x6700a122…8700
0x968279…9342
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0xa3a621f8f3…6975a2
Audit this contract →
← previous block·next block →recent activity