← previous blocknext block →recent activity
Analyzing
Block #86,924,117
11 transactions · 8 stateful · 2026-07-10 22:00:37 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,924,117 · 11 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x3a996b35…bc8f
0x34b655…2a6f
4 touches
1 conflict
0xe246730f…760d
0x34b655…2a6f
4 touches
1 conflict
0xeaed2cda…78bb
0x34b655…2a6f
4 touches
1 conflict
0xd1ec0dfd…ccc0
0xc8689a…ee79
4 touches
1 conflict
0x0a6a5b44…d0e5
0x34b655…2a6f
2 touches
0 conflicts
0x0d43cc69…6f83
0x34b655…2a6f
2 touches
0 conflicts
0x1dddd7ef…8f05
0x34b655…2a6f
2 touches
0 conflicts
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 0x6e90b9b1e7…73dca8
Audit this contract →
← previous block·next block →recent activity