← previous blocknext block →recent activity
Analyzing
Block #86,774,507
13 transactions · 10 stateful · 2026-07-10 05:20:32 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,774,507 · 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
5w08w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e9d86f5…53a8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c2e78a1…2f95
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x1e9d86f52e…f753a8
Audit this contract →
← previous block·next block →recent activity