← previous blocknext block →recent activity
Analyzing
Block #94,301,651
13 transactions · 13 stateful · 2026-08-08 20:36:09 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,301,651 · 13 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
2w03w14w25w06w17w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a05509d…d073
0x34b655…2a6f
8 touches
6 conflicts
0xc6b604e6…5152
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x27754bd4…96ae
0x34b655…2a6f
4 touches
1 conflict
0x5261f6ab…9aa1
0xee8c0e…1242
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
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 0x5a05509d59…77d073
Audit this contract →
← previous block·next block →recent activity