← previous blocknext block →recent activity
Analyzing
Block #86,671,407
10 transactions · 9 stateful · 2026-07-09 17:51:58 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,671,407 · 10 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
2w03w04w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7eab4979…0d6c
0x34b655…2a6f
4 touches
1 conflict
0x7eab4979…0d6d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6bd6b33e…9557
0x34b655…2a6f
4 touches
1 conflict
0x7e1faa73…bfbf
0x34b655…2a6f
4 touches
1 conflict
0xab4a9e70…a605
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
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 0x7eab4979b1…a40d6c
Audit this contract →
← previous block·next block →recent activity