← previous blocknext block →recent activity
Analyzing
Block #86,340,303
13 transactions · 12 stateful · 2026-07-08 04:56:35 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,340,303 · 13 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
3w04w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c366266…77e1
0x34b655…2a6f
4 touches
1 conflict
0x242bdfb5…974d
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0xb2c1bd58…621c
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7215
0x34b655…2a6f
4 touches
1 conflict
0x5b557bde…506c
0x34b655…2a6f
3 touches
1 conflict
0x1e04c5ec…8d51
0x34b655…2a6f
3 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 0x0c36626644…6d77e1
Audit this contract →
← previous block·next block →recent activity