← previous blocknext block →recent activity
Analyzing
Block #86,928,482
21 transactions · 16 stateful · 2026-07-10 22:29:45 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,928,482 · 21 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
2w03w17w08w19w210w311w414w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x3a192eef…3c7f
0x34b655…2a6f
4 touches
1 conflict
0x3a76803c…4181
0x34b655…2a6f
4 touches
1 conflict
0x45597879…8174
0x34b655…2a6f
4 touches
1 conflict
0x4aabcacf…c0ea
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity