← previous blocknext block →recent activity
Analyzing
Block #86,503,503
29 transactions · 20 stateful · 2026-07-08 23:07:07 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,503,503 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w110w214w015w116w219w221w322w423w426w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd6149e68…c994
0xd32edf…ff58
5 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0xd576a1b7…dead
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: Perpl
6 conflicts on slot 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity