← previous blocknext block →recent activity
Analyzing
Block #86,610,913
15 transactions · 13 stateful · 2026-07-09 11:06:41 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,610,913 · 15 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
5w06w17w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a37aad1…720f
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xa3e06ffb…6c2b
0x34b655…2a6f
4 touches
1 conflict
0xd040d680…4b05
0xb1dbf0…c0d3
3 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
3 touches
1 conflict
0xc3c11f4d…d857
0xb1dbf0…c0d3
3 touches
1 conflict
0x20238614…e0be
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x3a37aad12f…bb720f
Audit this contract →
← previous block·next block →recent activity