← previous blocknext block →recent activity
Analyzing
Block #86,764,226
16 transactions · 15 stateful · 2026-07-10 04:11:52 UTC
Parallelism
75/100
Blocked
60%
Avg conflicts / tx
1.06
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,764,226 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w17w28w39w210w111w212w014w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x10970e1d…90df
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x580babaa…1d26
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 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity