← previous blocknext block →recent activity
Analyzing
Block #86,624,910
30 transactions · 26 stateful · 2026-07-09 12:40:04 UTC
Parallelism
70/100
Blocked
46%
Avg conflicts / tx
1.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,624,910 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w310w013w416w117w520w424w525w626w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfcaee83d…428d
0x34b655…2a6f
8 touches
6 conflicts
0x1535d171…c68b
0x34b655…2a6f
8 touches
6 conflicts
0x1e48811e…2e39
0x34b655…2a6f
8 touches
6 conflicts
0x93701943…012b
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity