← previous blocknext block →recent activity
Analyzing
Block #86,626,779
25 transactions · 20 stateful · 2026-07-09 12:52:34 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,626,779 · 25 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
1w03w04w05w16w07w18w011w213w114w116w322w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity