← previous blocknext block →recent activity
Analyzing
Block #86,565,253
25 transactions · 16 stateful · 2026-07-09 06:00:23 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,565,253 · 25 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
1w03w14w05w213w016w017w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fde64da…aa3e
0x2a68ba…90c5
6 touches
3 conflicts
0xd4d41baf…81ad
0x851145…3f07
5 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x0fde64da0b…a5aa3e
Audit this contract →
← previous block·next block →recent activity