← previous blocknext block →recent activity
Analyzing
Block #86,789,316
18 transactions · 14 stateful · 2026-07-10 06:59:19 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,789,316 · 18 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
1w03w15w06w17w29w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6286219a…0721
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
5 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
5 touches
3 conflicts
0x7f430e47…4cbd
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d19f
0xb1dbf0…c0d3
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x6286219a51…db0721
Audit this contract →
← previous block·next block →recent activity