← previous blocknext block →recent activity
Analyzing
Block #86,319,027
22 transactions · 19 stateful · 2026-07-08 02:34:30 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,319,027 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w19w013w114w015w217w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0x57d82855…321d
0x851145…3f07
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x17e0d8a9…c98d
0xd32edf…ff58
3 touches
1 conflict
0xa23619a7…40e4
0x3bd359…433a
2 touches
0 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
1 conflict on slot 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity