← previous blocknext block →recent activity
Analyzing
Block #96,612,286
16 transactions · 14 stateful · 2026-08-16 22:44:40 UTC
Parallelism
75/100
Blocked
21%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,612,286 · 16 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x0de8f3e9…a865
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe1a9f808…b867
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x153d1e25…10ea
0x34b655…2a6f
2 touches
0 conflicts
0x1907196e…8745
0x34b655…2a6f
2 touches
0 conflicts
0x333ca5f2…9833
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 0x840d3ab7c3…edc8c4
Audit this contract →
← previous block·next block →recent activity