← previous blocknext block →recent activity
Analyzing
Block #92,855,524
14 transactions · 13 stateful · 2026-08-03 19:15:09 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,855,524 · 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
1w02w14w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x968279…9342
10 touches
10 conflicts
0xe5e57e99…e594
0x968279…9342
10 touches
10 conflicts
0xe5e57e99…e596
0x968279…9342
10 touches
10 conflicts
0xe978d646…dbb0
0x968279…9342
10 touches
10 conflicts
0xe978d646…dbb1
0x968279…9342
10 touches
10 conflicts
0xe978d646…dbb4
0x968279…9342
10 touches
10 conflicts
0xe978d646…dbb5
0x968279…9342
10 touches
10 conflicts
0xe5e57e99…e593
0x968279…9342
10 touches
10 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: 0x96827978…f09342
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity