← previous blocknext block →recent activity
Analyzing
Block #86,669,429
9 transactions · 7 stateful · 2026-07-09 17:38:44 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,669,429 · 9 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
2w03w04w15w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88413c1a…7783
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x95d63682…276d
0x34b655…2a6f
2 touches
0 conflicts
0x9836123e…0e41
0x34b655…2a6f
2 touches
0 conflicts
0x9836123e…0e42
0x34b655…2a6f
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 0x88413c1a8a…857783
Audit this contract →
← previous block·next block →recent activity