← previous blocknext block →recent activity
Analyzing
Block #96,308,417
12 transactions · 12 stateful · 2026-08-15 21:16:02 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,308,417 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1e38abf…f52a
0x968279…9342
10 touches
10 conflicts
0x521a5982…a82a
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x968279…9342
10 touches
10 conflicts
0x47060c40…e016
0x968279…9342
10 touches
10 conflicts
0x47060c40…e017
0x968279…9342
10 touches
10 conflicts
0x47060c40…e01a
0x968279…9342
10 touches
10 conflicts
0x47060c40…e01b
0x968279…9342
10 touches
10 conflicts
0x47060c40…e01c
0x968279…9342
10 touches
10 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
10 conflicts on slot 0xd1e38abf37…23f52a
Audit this contract →
← previous block·next block →recent activity