← previous blocknext block →recent activity
Analyzing
Block #94,235,259
13 transactions · 11 stateful · 2026-08-08 14:59:49 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,235,259 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd3d8226…d72f
0x34b655…2a6f
4 touches
1 conflict
0xfd3d8226…d730
0x34b655…2a6f
4 touches
1 conflict
0xaedb0755…6d93
0x34b655…2a6f
4 touches
1 conflict
0xb50784dd…8638
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xc2a722dc…1ef8
0x34b655…2a6f
4 touches
1 conflict
0x5994e814…9a96
0x34b655…2a6f
2 touches
0 conflicts
0x61439bd7…402a
0x34b655…2a6f
2 touches
0 conflicts
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 0xfd3d8226b8…c3d72f
Audit this contract →
← previous block·next block →recent activity