← previous blocknext block →recent activity
Analyzing
Block #83,614,592
40 transactions · 32 stateful · 2026-06-25 14:03:20 UTC
Parallelism
55/100
Blocked
69%
Avg conflicts / tx
3.83
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,614,592 · 40 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w29w311w412w415w016w117w218w319w420w521w622w723w824w925w1026w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x9af72ba2…f151
0x34b655…2a6f
16 touches
28 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
16 touches
28 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
16 touches
28 conflicts
0x678856fc…76ab
0x34b655…2a6f
11 touches
17 conflicts
0x6e1b71d7…8221
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 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