← previous blocknext block →recent activity
Analyzing
Block #94,058,737
7 transactions · 7 stateful · 2026-08-08 00:07:18 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,058,737 · 7 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
1w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad9673cd…ffd1
0x34b655…2a6f
4 touches
1 conflict
0x6b89ce6f…cc35
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x30d0e346…c76f
0x34b655…2a6f
2 touches
0 conflicts
0x518d5960…7960
0x34b655…2a6f
2 touches
0 conflicts
0x5b3f9959…fede
0x34b655…2a6f
2 touches
0 conflicts
0x5b3f9959…fedf
0x34b655…2a6f
2 touches
0 conflicts
0x61e01cd0…b73e
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 0xad9673cd61…d6ffd1
Audit this contract →
← previous block·next block →recent activity