← previous blocknext block →recent activity
Analyzing
Block #86,734,758
10 transactions · 7 stateful · 2026-07-10 00:54:54 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,734,758 · 10 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
4w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0x9b45750d…5923
0x34b655…2a6f
4 touches
1 conflict
0xf96f1cdc…d66e
0x34b655…2a6f
4 touches
1 conflict
0x75854a6e…5d6e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x75854a6e…5d6d
0x34b655…2a6f
4 touches
1 conflict
0x0178c2de…b37d
0xb1dbf0…c0d3
2 touches
0 conflicts
0x6a248bdc…3c1b
0xb1dbf0…c0d3
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 0x9a3463f0c8…ca0b73
Audit this contract →
← previous block·next block →recent activity