← previous blocknext block →recent activity
Analyzing
Block #83,758,303
53 transactions · 45 stateful · 2026-06-26 06:02:21 UTC
Parallelism
70/100
Blocked
80%
Avg conflicts / tx
4.08
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,758,303 · 53 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w19w210w011w312w013w314w415w516w617w718w819w920w1021w1122w1223w1343w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
22 touches
55 conflicts
0x40970e69…da50
0x69df8a…6292
18 touches
36 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
18 touches
36 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
18 touches
36 conflicts
0xdb067026…9eb8
0x69df8a…6292
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0x73a15040…bcef
0xa6afd3…d132
18 touches
36 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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity