← previous blocknext block →recent activity
Analyzing
Block #96,533,246
15 transactions · 14 stateful · 2026-08-16 16:07:07 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,533,246 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w19w010w111w212w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0a9b8ea…6214
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x17cf6835…83cb
0x968279…9342
8 touches
6 conflicts
0x17cf6835…83cc
0x968279…9342
8 touches
6 conflicts
0x17cf6835…83ce
0x968279…9342
8 touches
6 conflicts
0xe0a9b8ea…620d
0x968279…9342
8 touches
6 conflicts
0xe0a9b8ea…620e
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 0xe0a9b8ea9b…b16214
Audit this contract →
← previous block·next block →recent activity