← previous blocknext block →recent activity
Analyzing
Block #86,709,312
17 transactions · 15 stateful · 2026-07-09 22:04:53 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,709,312 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w09w012w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98d58911…19f2
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48fb2063…4025
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x63b15849…80b2
0x34b655…2a6f
4 touches
1 conflict
0xb46ee126…a1a5
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 0x98d589117f…0c19f2
Audit this contract →
← previous block·next block →recent activity