← previous blocknext block →recent activity
Analyzing
Block #86,619,022
25 transactions · 20 stateful · 2026-07-09 12:00:49 UTC
Parallelism
84/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,619,022 · 25 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
1w03w112w013w114w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xfcf4fbc8…19f5
0x065c9d…c394
4 touches
1 conflict
0x6a248bdc…3c1b
0xb1dbf0…c0d3
4 touches
1 conflict
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0x7f430e47…4cbd
0xb1dbf0…c0d3
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x8a35acfbc1…6bd1a9
Audit this contract →
← previous block·next block →recent activity