← previous blocknext block →recent activity
Analyzing
Block #86,829,527
13 transactions · 12 stateful · 2026-07-10 11:28:13 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,829,527 · 13 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
1w02w03w16w27w38w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x1d720942…075a
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xfc90a885…60ad
0x34b655…2a6f
4 touches
1 conflict
0xfc90a885…60ae
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity