← previous blocknext block →recent activity
Analyzing
Block #96,424,291
15 transactions · 10 stateful · 2026-08-16 06:58:48 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,424,291 · 15 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
6w010w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x632a3f89…c958
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x785c87ba…a0f1
0x34b655…2a6f
4 touches
1 conflict
0xb416438e…796a
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
2 touches
0 conflicts
0x35b0198e…3e0d
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
6 conflicts on slot 0x632a3f898d…c8c958
Audit this contract →
← previous block·next block →recent activity