← previous blocknext block →recent activity
Analyzing
Block #86,488,016
16 transactions · 14 stateful · 2026-07-08 21:23:48 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,488,016 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w210w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x080ec687…da80
0x34b655…2a6f
6 touches
3 conflicts
0xd16df6cd…5532
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3f24a374…6bc3
0x34b655…2a6f
6 touches
3 conflicts
0x6e334aa4…583b
0x34b655…2a6f
4 touches
1 conflict
0xa8b7b7ec…f634
0x34b655…2a6f
4 touches
1 conflict
0xb577a4a7…a670
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
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
3 conflicts on slot 0x080ec68796…07da80
Audit this contract →
← previous block·next block →recent activity