← previous blocknext block →recent activity
Analyzing
Block #86,845,631
21 transactions · 18 stateful · 2026-07-10 13:15:50 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,845,631 · 21 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
1w02w18w011w114w018w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3343d6f…bbde
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbdf
0x34b655…2a6f
4 touches
1 conflict
0xfc1a42e4…e1e8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
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
1 conflict on slot 0xf3343d6fb5…09bbde
Audit this contract →
← previous block·next block →recent activity