← previous blocknext block →recent activity
Analyzing
Block #86,668,690
14 transactions · 14 stateful · 2026-07-09 17:33:48 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,668,690 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5238dcb7…e0e2
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x143dba04…1b98
0xb1dbf0…c0d3
3 touches
1 conflict
0x1e451306…7993
0xb1dbf0…c0d3
3 touches
1 conflict
0xe5d48e35…6b67
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 0x5238dcb768…51e0e2
Audit this contract →
← previous block·next block →recent activity