← previous blocknext block →recent activity
Analyzing
Block #86,708,813
17 transactions · 16 stateful · 2026-07-09 22:01:33 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,708,813 · 17 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
2w03w19w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x0bc74d87…b9ca
0x34b655…2a6f
4 touches
1 conflict
0x1bfc029c…f91e
0x34b655…2a6f
4 touches
1 conflict
0x2026a818…d297
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x288bc578…318e
0x34b655…2a6f
4 touches
1 conflict
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x6f0819df…347b
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 0x03fb27fddd…f00c06
Audit this contract →
← previous block·next block →recent activity