← previous blocknext block →recent activity
Analyzing
Block #86,633,160
16 transactions · 14 stateful · 2026-07-09 13:35:16 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,633,160 · 16 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
3w05w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a38e46…a68c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf06ab8d8…3589
0x34b655…2a6f
4 touches
1 conflict
0x326f2a00…a2a6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa6c4c171…5da8
0x34b655…2a6f
2 touches
0 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1542
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 0xe5a38e469a…0da68c
Audit this contract →
← previous block·next block →recent activity