← previous blocknext block →recent activity
Analyzing
Block #86,386,310
24 transactions · 20 stateful · 2026-07-08 10:04:04 UTC
Parallelism
92/100
Blocked
15%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,386,310 · 24 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
1w010w114w016w118w021w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c366266…77e1
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x7701846c…9b82
0x851145…3f07
4 touches
1 conflict
0x4318a7cf…3cd6
0xd32edf…ff58
3 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
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 0x0c36626644…6d77e1
Audit this contract →
← previous block·next block →recent activity