← previous blocknext block →recent activity
Analyzing
Block #86,539,818
25 transactions · 18 stateful · 2026-07-09 03:09:40 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,539,818 · 25 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
1w02w15w06w18w09w113w214w021w122w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xb5dbfa41…42b6
0x40c49f…2af0
4 touches
1 conflict
0x143dba04…1b98
0xb1dbf0…c0d3
4 touches
1 conflict
0x1e451306…7993
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity