← previous blocknext block →recent activity
Analyzing
Block #86,814,520
13 transactions · 11 stateful · 2026-07-10 09:47:41 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,814,520 · 13 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
3w04w17w08w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e463d17…0207
0x34b655…2a6f
4 touches
1 conflict
0xa4c4b591…7f9f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x038c21c9…fb45
0x34b655…2a6f
4 touches
1 conflict
0x30825136…2753
0x34b655…2a6f
4 touches
1 conflict
0x33c7a9e0…4810
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
1 conflict on slot 0x9e463d17c8…180207
Audit this contract →
← previous block·next block →recent activity