← previous blocknext block →recent activity
Analyzing
Block #86,817,556
12 transactions · 10 stateful · 2026-07-10 10:08:00 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,817,556 · 12 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06917e8…6985
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0a5a4598…01bc
0x34b655…2a6f
2 touches
0 conflicts
0x0ee13be7…7b2c
0x34b655…2a6f
2 touches
0 conflicts
0x7b6c252d…a696
0x34b655…2a6f
2 touches
0 conflicts
0xf0ad9713…5796
0x34b655…2a6f
2 touches
0 conflicts
0x3d727230…9c67
0x699abc…6a3b
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 0xb06917e887…5e6985
Audit this contract →
← previous block·next block →recent activity