← previous blocknext block →recent activity
Analyzing
Block #86,776,621
20 transactions · 18 stateful · 2026-07-10 05:34:37 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,776,621 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w211w312w413w416w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44485f70…b1ac
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0xe8927855…7e59
0x34b655…2a6f
4 touches
1 conflict
0xefcaccf2…c083
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
6 conflicts on slot 0x44485f7033…50b1ac
Audit this contract →
← previous block·next block →recent activity