← previous blocknext block →recent activity
Analyzing
Block #86,846,161
19 transactions · 14 stateful · 2026-07-10 13:19:22 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,846,161 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w07w18w110w112w113w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a59f9d3…57a8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xdb88134d…d6c1
0x34b655…2a6f
4 touches
1 conflict
0xdb88134d…d6c2
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x39d97e2c…b8c1
0x34b655…2a6f
3 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
1 conflict on slot 0x4a59f9d3ab…0b57a8
Audit this contract →
← previous block·next block →recent activity