← previous blocknext block →recent activity
Analyzing
Block #86,929,196
16 transactions · 13 stateful · 2026-07-10 22:34:31 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,929,196 · 16 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
1w02w16w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x552ac70a…d74b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1ba5d36c…9336
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x47d4745e…02bb
0x336ed4…c59c
4 touches
1 conflict
0xf72a90c2…830b
0x34b655…2a6f
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
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 0x552ac70aef…c8d74b
Audit this contract →
← previous block·next block →recent activity