← previous blocknext block →recent activity
Analyzing
Block #96,482,643
14 transactions · 12 stateful · 2026-08-16 11:52:18 UTC
Parallelism
43/100
Blocked
58%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,482,643 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2a6cf5a…d3ae
0x968279…9342
16 touches
28 conflicts
0x521a5982…a82a
0x754704…b603
16 touches
28 conflicts
0x00000000…0006
0x968279…9342
16 touches
28 conflicts
0x135c0d01…1c8c
0x968279…9342
16 touches
28 conflicts
0x135c0d01…1c8d
0x968279…9342
16 touches
28 conflicts
0x135c0d01…1c90
0x968279…9342
16 touches
28 conflicts
0x135c0d01…1c91
0x968279…9342
16 touches
28 conflicts
0x135c0d01…1c93
0x968279…9342
16 touches
28 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
28 conflicts on slot 0xb2a6cf5ae2…52d3ae
Audit this contract →
← previous block·next block →recent activity