← previous blocknext block →recent activity
Analyzing
Block #86,136,575
18 transactions · 17 stateful · 2026-07-07 06:16:15 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.61
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,136,575 · 18 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
1w02w13w04w15w06w18w110w011w112w113w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x29c1a140…099f
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x4ca9afe5…748d
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x9c1a0106…de12
0x34b655…2a6f
4 touches
1 conflict
0xaf9ccdb1…d44d
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity