← previous blocknext block →recent activity
Analyzing
Block #86,339,677
44 transactions · 29 stateful · 2026-07-08 04:52:24 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.27
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,339,677 · 44 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w29w311w312w413w426w427w529w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
10 touches
10 conflicts
0x8131fcdf…9761
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x503b3a72…f6df
0x34b655…2a6f
8 touches
6 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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity