← previous blocknext block →recent activity
Analyzing
Block #96,536,321
17 transactions · 16 stateful · 2026-08-16 16:22:35 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,536,321 · 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
5w06w08w09w110w211w312w413w514w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe624d0c7…5299
0x968279…9342
12 touches
15 conflicts
0x521a5982…a82a
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0xcb9a4488…1492
0x968279…9342
12 touches
15 conflicts
0xcb9a4488…1493
0x968279…9342
12 touches
15 conflicts
0xcb9a4488…1495
0x968279…9342
12 touches
15 conflicts
0xe624d0c7…5292
0x968279…9342
12 touches
15 conflicts
0xe624d0c7…5293
0x968279…9342
12 touches
15 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
15 conflicts on slot 0xe624d0c79a…985299
Audit this contract →
← previous block·next block →recent activity