← previous blocknext block →recent activity
Analyzing
Block #86,816,584
16 transactions · 13 stateful · 2026-07-10 10:01:30 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,816,584 · 16 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
1w02w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa58f1d73…9ce1
0x34b655…2a6f
4 touches
1 conflict
0xedcfbee7…ea97
0x34b655…2a6f
4 touches
1 conflict
0xa58f1d73…9ce0
0x34b655…2a6f
4 touches
1 conflict
0x6ba20cf2…c012
0xd32edf…ff58
3 touches
1 conflict
0x039c2f44…9ac7
0x34b655…2a6f
2 touches
0 conflicts
0x0921c970…9f93
0x34b655…2a6f
2 touches
0 conflicts
0x1586ff62…0ebe
0x34b655…2a6f
2 touches
0 conflicts
0x1586ff62…0ebf
0x34b655…2a6f
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 0xa58f1d73c9…079ce1
Audit this contract →
← previous block·next block →recent activity