← previous blocknext block →recent activity
Analyzing
Block #92,808,014
22 transactions · 21 stateful · 2026-08-03 15:16:01 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,808,014 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w26w38w411w012w113w214w015w116w219w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xebcced98…084d
0x968279…9342
6 touches
3 conflicts
0xe1722e22…1b9c
0x968279…9342
6 touches
3 conflicts
0xe1722e22…1b9e
0x968279…9342
6 touches
3 conflicts
0xebcced98…0848
0x968279…9342
6 touches
3 conflicts
0xebcced98…0849
0x968279…9342
6 touches
3 conflicts
0xebcced98…084c
0x968279…9342
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity