← previous blocknext block →recent activity
Analyzing
Block #96,352,411
12 transactions · 12 stateful · 2026-08-16 00:57:18 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,352,411 · 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
2w03w17w28w39w410w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda95d80c…a64c
0x34b655…2a6f
4 touches
1 conflict
0xf18c12c4…3e7d
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x4b13022d…dc04
0x34b655…2a6f
4 touches
1 conflict
0x6f97afda…faec
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity