← previous blocknext block →recent activity
Analyzing
Block #94,465,398
12 transactions · 10 stateful · 2026-08-09 10:28:30 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,465,398 · 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
1w02w13w24w35w47w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8a56a8f…3924
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa95fdd09…a6e8
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0xa8a50028…fed6
0x34b655…2a6f
4 touches
1 conflict
0xfc421e5f…71c0
0x34b655…2a6f
4 touches
1 conflict
0x096c7f83…68af
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 0xa8a56a8ff0…573924
Audit this contract →
← previous block·next block →recent activity