← previous blocknext block →recent activity
Analyzing
Block #86,856,463
19 transactions · 18 stateful · 2026-07-10 14:28:14 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,856,463 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w09w110w212w114w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71658d1a…f1ec
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
6 touches
3 conflicts
0x4dadca88…58d3
0x34b655…2a6f
6 touches
3 conflicts
0x516ec46d…fc46
0x34b655…2a6f
6 touches
3 conflicts
0x5e02109f…c11b
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
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 0x71658d1a59…90f1ec
Audit this contract →
← previous block·next block →recent activity