← previous blocknext block →recent activity
Analyzing
Block #86,325,004
13 transactions · 9 stateful · 2026-07-08 03:14:26 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,325,004 · 13 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
1w06w07w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3c18c18f…4322
0x065c9d…c394
2 touches
0 conflicts
0xb7f910ae…14dc
0x065c9d…c394
2 touches
0 conflicts
0xc24c26b4…ad6f
0x065c9d…c394
2 touches
0 conflicts
0xce43dad6…680a
0x065c9d…c394
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 0xa5a8ffca31…818de2
Audit this contract →
← previous block·next block →recent activity