← previous blocknext block →recent activity
Analyzing
Block #86,623,686
20 transactions · 16 stateful · 2026-07-09 12:31:56 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,623,686 · 20 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
1w02w13w24w05w16w27w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a7
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x143dba04…1b98
0xb1dbf0…c0d3
4 touches
1 conflict
0x1e451306…7993
0xb1dbf0…c0d3
4 touches
1 conflict
0x6286219a…0721
0xb1dbf0…c0d3
4 touches
1 conflict
0x6a248bdc…3c1b
0xb1dbf0…c0d3
4 touches
1 conflict
0xb07a0849…3b62
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
6 conflicts on slot 0x8a35acfbc1…6bd1a7
Audit this contract →
← previous block·next block →recent activity