← previous blocknext block →recent activity
Analyzing
Block #86,754,574
16 transactions · 15 stateful · 2026-07-10 03:07:26 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,754,574 · 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
1w03w04w15w27w38w411w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b4a7e2f…dc49
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x88692611…d222
0x34b655…2a6f
6 touches
3 conflicts
0x015c6c43…fa59
0x34b655…2a6f
4 touches
1 conflict
0x07ed27ca…3903
0x34b655…2a6f
4 touches
1 conflict
0x0ee13be7…7b2c
0x34b655…2a6f
4 touches
1 conflict
0xed4a0d72…065f
0x34b655…2a6f
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
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 0x1b4a7e2f5c…3edc49
Audit this contract →
← previous block·next block →recent activity