← previous blocknext block →recent activity
Analyzing
Block #93,538,399
14 transactions · 14 stateful · 2026-08-06 04:30:37 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,538,399 · 14 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
2w04w15w26w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6ae4a…90cb
0x34b655…2a6f
8 touches
6 conflicts
0xef80d1f6…7d6a
0x968279…9342
6 touches
3 conflicts
0x258a0d27…2d87
0x968279…9342
6 touches
3 conflicts
0x258a0d27…2d8a
0x968279…9342
6 touches
3 conflicts
0x258a0d27…2d8b
0x968279…9342
6 touches
3 conflicts
0x258a0d27…2d8d
0x968279…9342
6 touches
3 conflicts
0xef80d1f6…7d67
0x968279…9342
6 touches
3 conflicts
0xef80d1f6…7d68
0x968279…9342
6 touches
3 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
6 conflicts on slot 0x9ba6ae4a28…c990cb
Audit this contract →
← previous block·next block →recent activity