← previous blocknext block →recent activity
Analyzing
Block #94,835,454
17 transactions · 17 stateful · 2026-08-10 17:31:22 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,835,454 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w17w28w09w110w211w312w313w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb51b911…ac9c
0x968279…9342
8 touches
6 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x81370291…40df
0x968279…9342
8 touches
6 conflicts
0x81370291…40e1
0x968279…9342
8 touches
6 conflicts
0xcb51b911…ac95
0x968279…9342
8 touches
6 conflicts
0xcb51b911…ac96
0x968279…9342
8 touches
6 conflicts
0xcb51b911…ac99
0x968279…9342
8 touches
6 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
6 conflicts on slot 0xcb51b91140…71ac9c
Audit this contract →
← previous block·next block →recent activity