← previous blocknext block →recent activity
Analyzing
Block #83,659,331
41 transactions · 36 stateful · 2026-06-25 19:02:08 UTC
Parallelism
73/100
Blocked
67%
Avg conflicts / tx
1.8
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,659,331 · 41 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w19w210w312w013w116w117w218w119w220w325w227w428w229w430w331w433w535w736w837w938w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x8617c94f…6193
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x75cdffd8…c217
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
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
28 conflicts on slot 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity