← previous blocknext block →recent activity
Analyzing
Block #86,678,232
14 transactions · 12 stateful · 2026-07-09 18:37:29 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,678,232 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w19w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb52189ea…8281
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a3ca58e…6490
0x851145…3f07
4 touches
1 conflict
0x6a248bdc…3c1b
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1aa
0xb1dbf0…c0d3
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
1 conflict on slot 0xb52189ea0f…d68281
Audit this contract →
← previous block·next block →recent activity