← previous blocknext block →recent activity
Analyzing
Block #85,572,343
16 transactions · 14 stateful · 2026-07-04 15:34:06 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,572,343 · 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
2w03w14w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x26ffd5ab…63e1
0x065c9d…c394
4 touches
1 conflict
0xafcd541d…7d20
0x065c9d…c394
3 touches
1 conflict
0xcc269840…c489
0x065c9d…c394
3 touches
1 conflict
0x4b5f9925…d147
0x065c9d…c394
3 touches
1 conflict
0x31a4ade5…dfc8
0x065c9d…c394
3 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
2 touches
0 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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity