← previous blocknext block →recent activity
Analyzing
Block #85,124,271
43 transactions · 35 stateful · 2026-07-02 13:49:51 UTC
Parallelism
60/100
Blocked
71%
Avg conflicts / tx
2.28
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #85,124,271 · 43 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w314w015w117w218w319w420w524w426w227w528w130w132w735w1037w1239w1441w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x59645a97…3ca1
0x34b655…2a6f
12 touches
15 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
10 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x9579025c…c3ec
0x34b655…2a6f
8 touches
6 conflicts
0x0934ec4c…50c8
0x34b655…2a6f
8 touches
6 conflicts
0xbc04d98e…a484
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity