← previous blocknext block →recent activity
Analyzing
Block #84,522,768
21 transactions · 20 stateful · 2026-06-29 18:57:34 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,522,768 · 21 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
1w02w16w07w19w210w312w313w214w318w019w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7763f6…89be
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe4afaa2f…3b69
0xa6afd3…d132
6 touches
3 conflicts
0x019ded9d…6fa0
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xe27b0bdf…b21a
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 0x1c7763f6c9…dd89be
Audit this contract →
← previous block·next block →recent activity