← previous blocknext block →recent activity
Analyzing
Block #85,773,114
27 transactions · 24 stateful · 2026-07-05 13:52:11 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,773,114 · 27 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
1w02w03w14w27w08w19w210w313w214w117w018w119w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x66845e6f…b6bd
0x065c9d…c394
4 touches
1 conflict
0x66f473d3…2d03
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xa90ff50e…4292
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: 0x04fdeac2…f747d7
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity