← previous blocknext block →recent activity
Analyzing
Block #86,448,670
13 transactions · 11 stateful · 2026-07-08 17:00:32 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,448,670 · 13 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
1w02w03w05w16w18w011w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66e6480e…c384
0x40c49f…2af0
4 touches
1 conflict
0x080ec687…da80
0x34b655…2a6f
4 touches
1 conflict
0x13a10b08…c859
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0x66e6480edd…32c384
Audit this contract →
← previous block·next block →recent activity