← previous blocknext block →recent activity
Analyzing
Block #86,360,630
12 transactions · 10 stateful · 2026-07-08 07:12:16 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,360,630 · 12 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
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x241bf15c…76a9
0x34b655…2a6f
3 touches
1 conflict
0x5e14cf2d…b92a
0x34b655…2a6f
3 touches
1 conflict
0x94623194…97c1
0x34b655…2a6f
3 touches
1 conflict
0x2802b975…ef4d
0x065c9d…c394
2 touches
0 conflicts
0xc72e3b29…37ec
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity