← previous blocknext block →recent activity
Analyzing
Block #94,289,724
12 transactions · 8 stateful · 2026-08-08 19:35:49 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,289,724 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0213a0a…ff34
0x34b655…2a6f
4 touches
1 conflict
0xd81dbbb9…d0c5
0x34b655…2a6f
4 touches
1 conflict
0xd8675136…9a01
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x21ef0807…d889
0x34b655…2a6f
4 touches
1 conflict
0x2c66ecd1…f41d
0x34b655…2a6f
4 touches
1 conflict
0x3b2c8363…a429
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 0xf0213a0a5f…6bff34
Audit this contract →
← previous block·next block →recent activity