← previous blocknext block →recent activity
Analyzing
Block #86,807,119
25 transactions · 20 stateful · 2026-07-10 08:58:13 UTC
Parallelism
84/100
Blocked
60%
Avg conflicts / tx
0.84
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,807,119 · 25 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
1w02w14w25w06w17w210w011w114w215w117w218w319w320w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb804398…970e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xcb8043986c…ff970e
Audit this contract →
← previous block·next block →recent activity