← previous blocknext block →recent activity
Analyzing
Block #86,711,829
16 transactions · 14 stateful · 2026-07-09 22:21:40 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,711,829 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70ff9262…8d80
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x11f0c3b4…7643
0x40c49f…2af0
2 touches
0 conflicts
0x5810d46e…a995
0x40c49f…2af0
2 touches
0 conflicts
0x65214d60…609a
0x40c49f…2af0
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 0x70ff92623d…f38d80
Audit this contract →
← previous block·next block →recent activity