← previous blocknext block →recent activity
Analyzing
Block #95,852,790
16 transactions · 15 stateful · 2026-08-14 07:03:50 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,852,790 · 16 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
1w05w06w07w18w19w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x015bcfcb…c10c
0x34b655…2a6f
6 touches
3 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
6 touches
3 conflicts
0x44330547…f55e
0x851145…3f07
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0xb9f0b0dc…4827
0x34b655…2a6f
4 touches
1 conflict
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0x015bcfcbf4…cfc10c
Audit this contract →
← previous block·next block →recent activity