← previous blocknext block →recent activity
Analyzing
Block #94,859,101
12 transactions · 11 stateful · 2026-08-10 19:30:20 UTC
Parallelism
50/100
Blocked
73%
Avg conflicts / tx
1.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,859,101 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w39w410w511w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x535cd929…07ce
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0x981b7617…6093
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity