← previous blocknext block →recent activity
Analyzing
Block #86,917,017
24 transactions · 18 stateful · 2026-07-10 21:13:06 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,917,017 · 24 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
1w04w17w08w09w115w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x74fa2096…56ea
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc2eab074…c77b
0xd32edf…ff58
3 touches
1 conflict
0x610e1ac5…1444
0x065c9d…c394
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
2 touches
0 conflicts
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 0x5d46e6a0b6…d15ed9
Audit this contract →
← previous block·next block →recent activity