← previous blocknext block →recent activity
Analyzing
Block #86,741,737
22 transactions · 20 stateful · 2026-07-10 01:41:35 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,741,737 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w211w312w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x5d863b2f…bd28
0x34b655…2a6f
6 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0xb975916d…b00b
0x34b655…2a6f
4 touches
1 conflict
0xa05860b1…782e
0x34b655…2a6f
4 touches
1 conflict
0x1082298a…e05e
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity