← previous blocknext block →recent activity
Analyzing
Block #86,713,504
30 transactions · 18 stateful · 2026-07-09 22:32:52 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,713,504 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
12w013w115w018w119w227w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x3b4d64bb…c98d
0x34b655…2a6f
4 touches
1 conflict
0x5d010bea…4107
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4b
0x34b655…2a6f
4 touches
1 conflict
0x64800813…db9f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity