← previous blocknext block →recent activity
Analyzing
Block #85,875,027
29 transactions · 19 stateful · 2026-07-06 01:10:59 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,875,027 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x33bd5ec4…af53
0xa6afd3…d132
4 touches
1 conflict
0xc7a15219…7745
0xa6afd3…d132
4 touches
1 conflict
0xfa067a8f…a842
0xa6afd3…d132
3 touches
1 conflict
0x7a44ef23…6f53
0x40c49f…2af0
2 touches
0 conflicts
0x80874025…1c8f
0x40c49f…2af0
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: 0x04fdeac2…f747d7
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity