← previous blocknext block →recent activity
Analyzing
Block #86,503,218
18 transactions · 17 stateful · 2026-07-08 23:05:13 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,503,218 · 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
6w07w08w09w110w011w112w213w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x6ede85f4…0b8a
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8b
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b416
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b418
0x928dc8…8207
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x613560f2…8d9e
0x928dc8…8207
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 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity