← previous blocknext block →recent activity
Analyzing
Block #93,229,708
14 transactions · 14 stateful · 2026-08-05 02:38:39 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,229,708 · 14 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
1w02w05w06w17w29w310w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e2c4afe…90a4
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xb5924647…4cf1
0x34b655…2a6f
6 touches
3 conflicts
0xe0e00683…e335
0x34b655…2a6f
6 touches
3 conflicts
0x7da6eb60…b34e
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 0x4e2c4afe9d…0690a4
Audit this contract →
← previous block·next block →recent activity