← previous blocknext block →recent activity
Analyzing
Block #86,954,250
18 transactions · 16 stateful · 2026-07-11 01:21:54 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,954,250 · 18 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
1w04w05w16w07w08w011w113w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8a876d4…921a
0xb1dbf0…c0d3
4 touches
1 conflict
0x4af2cce5…16c4
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x350e5d8a…601f
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
1 conflict on slot 0xe8a876d421…11921a
Audit this contract →
← previous block·next block →recent activity