← previous blocknext block →recent activity
Analyzing
Block #86,665,726
14 transactions · 14 stateful · 2026-07-09 17:14:01 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,665,726 · 14 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
1w02w03w18w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a6e42c5…9438
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x9ebf11a0…86e4
0xd32edf…ff58
3 touches
1 conflict
0x13b50d83…767f
0x065c9d…c394
2 touches
0 conflicts
0xcc3cbaa1…9fc4
0x065c9d…c394
2 touches
0 conflicts
0xffd4973f…0b39
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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 0x6a6e42c571…c39438
Audit this contract →
← previous block·next block →recent activity