← previous blocknext block →recent activity
Analyzing
Block #86,819,775
24 transactions · 21 stateful · 2026-07-10 10:22:49 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,819,775 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w09w110w211w314w015w116w219w121w022w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x19ba76c3…6342
0x34b655…2a6f
6 touches
3 conflicts
0xfee72f1e…0aee
0x34b655…2a6f
6 touches
3 conflicts
0x7eab4979…0d6d
0x34b655…2a6f
4 touches
1 conflict
0xab4a9e70…a605
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity