← previous blocknext block →recent activity
Analyzing
Block #86,453,238
16 transactions · 14 stateful · 2026-07-08 17:31:05 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,453,238 · 16 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
1w06w08w110w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5dbfacf…c5ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1552bf3…80a3
0xd32edf…ff58
3 touches
1 conflict
0xd9ffa66b…8b05
0x1efe02…37d6
2 touches
0 conflicts
0xee205fb8…6101
0x1efe02…37d6
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xd5dbfacf04…49c5ec
Audit this contract →
← previous block·next block →recent activity