← previous blocknext block →recent activity
Analyzing
Block #83,615,936
69 transactions · 51 stateful · 2026-06-25 14:12:20 UTC
Parallelism
65/100
Blocked
75%
Avg conflicts / tx
4.65
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #83,615,936 · 69 txs across 24 waves · depth 24
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
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w010w113w216w319w422w525w626w756w159w165w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
48 touches
276 conflicts
0x2484cc15…5afc
0x34b655…2a6f
28 touches
91 conflicts
0xe02484a6…c32e
0xc8689a…ee79
28 touches
91 conflicts
0x5941ac48…c525
0x34b655…2a6f
28 touches
91 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
28 touches
91 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xdb067026…9eb8
0x69df8a…6292
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
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
276 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity