← previous blocknext block →recent activity
Analyzing
Block #96,838,718
16 transactions · 15 stateful · 2026-08-17 17:43:32 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,838,718 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w38w49w513w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x8eef368f…aa21
0x34b655…2a6f
12 touches
15 conflicts
0x4ca37118…3c71
0x34b655…2a6f
8 touches
6 conflicts
0x334b15f3…045c
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity