← previous blocknext block →recent activity
Analyzing
Block #95,737,802
20 transactions · 20 stateful · 2026-08-13 21:25:29 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,737,802 · 20 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
4w05w16w07w18w29w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd0b5f8…f7f9
0x34b655…2a6f
6 touches
3 conflicts
0x570471ef…7a75
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc4ac7154…0aeb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc845ad2a…8e63
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x9fd0b5f8b3…d4f7f9
Audit this contract →
← previous block·next block →recent activity