← previous blocknext block →recent activity
Analyzing
Block #86,989,988
16 transactions · 15 stateful · 2026-07-11 05:20:43 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,989,988 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w210w111w312w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x814f0f40…c654
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfc4d32c0…39f9
0x34b655…2a6f
6 touches
3 conflicts
0x79e5df76…64ee
0x34b655…2a6f
6 touches
3 conflicts
0x25f0d803…174e
0x34b655…2a6f
6 touches
3 conflicts
0x25f0d803…174f
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
10 conflicts on slot 0x814f0f40f3…5dc654
Audit this contract →
← previous block·next block →recent activity