← previous blocknext block →recent activity
Analyzing
Block #96,827,832
10 transactions · 8 stateful · 2026-08-17 16:48:46 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,827,832 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bf1c03f…c440
0x34b655…2a6f
6 touches
3 conflicts
0x87d62b39…b5ab
0x34b655…2a6f
4 touches
1 conflict
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0x17fb2c40…8e52
0x34b655…2a6f
2 touches
0 conflicts
0x1caf0c05…15ce
0x34b655…2a6f
2 touches
0 conflicts
0x26242d99…39ae
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
0x34b655…2a6f
2 touches
0 conflicts
0x4175950a…1dfe
0x34b655…2a6f
2 touches
0 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: Perpl
3 conflicts on slot 0x7bf1c03f1a…d1c440
Audit this contract →
← previous block·next block →recent activity