← previous blocknext block →recent activity
Analyzing
Block #86,293,469
14 transactions · 11 stateful · 2026-07-07 23:43:41 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,293,469 · 14 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
2w03w14w26w08w112w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x077d58c3…8ed7
0x34b655…2a6f
6 touches
3 conflicts
0xffb8950c…23c6
0x34b655…2a6f
6 touches
3 conflicts
0x6762cac2…3fb0
0x34b655…2a6f
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x808415c0…7f83
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
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
3 conflicts on slot 0x077d58c3dc…178ed7
Audit this contract →
← previous block·next block →recent activity