← previous blocknext block →recent activity
Analyzing
Block #86,913,969
14 transactions · 12 stateful · 2026-07-10 20:52:46 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,913,969 · 14 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
2w03w17w08w19w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2efac4f6…3abf
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2003acab…0b17
0x34b655…2a6f
4 touches
1 conflict
0x2bc13458…e6d8
0x34b655…2a6f
4 touches
1 conflict
0x2bc13458…e6d9
0x34b655…2a6f
4 touches
1 conflict
0x3034af96…e290
0x34b655…2a6f
4 touches
1 conflict
0x58126412…4dad
0x34b655…2a6f
4 touches
1 conflict
0x6363986b…fe3a
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 0x2efac4f6c8…eb3abf
Audit this contract →
← previous block·next block →recent activity