← previous blocknext block →recent activity
Analyzing
Block #96,600,252
16 transactions · 15 stateful · 2026-08-16 21:44:08 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,600,252 · 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
2w05w16w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5376f5ee…5daa
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xafbbdaaf…448a
0x34b655…2a6f
4 touches
1 conflict
0x3226e3fe…f799
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
3 conflicts on slot 0x5376f5ee4e…8a5daa
Audit this contract →
← previous block·next block →recent activity