← previous blocknext block →recent activity
Analyzing
Block #86,945,604
16 transactions · 16 stateful · 2026-07-11 00:24:11 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,945,604 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w310w412w113w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
7 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x5a3732cb…edb1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: Perpl
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity