← previous blocknext block →recent activity
Analyzing
Block #86,979,092
13 transactions · 12 stateful · 2026-07-11 04:07:53 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,979,092 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
4 touches
1 conflict
0x0178c2de…b37d
0xb1dbf0…c0d3
4 touches
1 conflict
0x0335ae80…8414
0xb1dbf0…c0d3
4 touches
1 conflict
0x74825c4e…32e9
0xb1dbf0…c0d3
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9d1bb389…c7d9
0xb1dbf0…c0d3
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…6bd1a8
Audit this contract →
← previous block·next block →recent activity