← previous blocknext block →recent activity
Analyzing
Block #86,058,846
28 transactions · 27 stateful · 2026-07-06 21:37:32 UTC
Parallelism
61/100
Blocked
63%
Avg conflicts / tx
2.32
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,058,846 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w19w210w311w412w513w614w715w816w917w1021w124w227w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
22 touches
55 conflicts
0x28681974…b88f
0xa6afd3…d132
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x29418a3d…8c6e
0x34b655…2a6f
4 touches
1 conflict
0x756913cf…e7bd
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0xd8bc53a3…c2fe
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: 0x04fdeac2…f747d7
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity