← previous blocknext block →recent activity
Analyzing
Block #86,741,970
20 transactions · 17 stateful · 2026-07-10 01:43:09 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,741,970 · 20 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
1w02w14w05w18w29w210w311w412w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x636fd21a…9978
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x68745dec…328f
0x34b655…2a6f
6 touches
3 conflicts
0x5d6582e8…79a1
0xd32edf…ff58
5 touches
3 conflicts
0x485ae99d…f26f
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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 0x636fd21a61…849978
Audit this contract →
← previous block·next block →recent activity