← previous blocknext block →recent activity
Analyzing
Block #86,964,733
23 transactions · 22 stateful · 2026-07-11 02:32:01 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,964,733 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w09w010w111w012w113w114w215w316w320w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x139d81fd…118a
0xd32edf…ff58
5 touches
3 conflicts
0xdc9ac610…217d
0x065c9d…c394
4 touches
1 conflict
0x21db5c5e…e6f9
0x34b655…2a6f
4 touches
1 conflict
0x5b9e5ecc…2bc7
0x34b655…2a6f
4 touches
1 conflict
0x6fd328f3…701f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xb6ed530c56…eed450
Audit this contract →
← previous block·next block →recent activity