← previous blocknext block →recent activity
Analyzing
Block #83,623,905
56 transactions · 43 stateful · 2026-06-25 15:05:38 UTC
Parallelism
68/100
Blocked
72%
Avg conflicts / tx
3.14
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,623,905 · 56 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
1w02w13w24w35w06w08w19w213w215w316w418w520w144w1547w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
14 touches
21 conflicts
0xab981df1…2941
0x34b655…2a6f
14 touches
21 conflicts
0xc2dcae88…f07a
0x34b655…2a6f
14 touches
21 conflicts
0x0b408000…9df1
0x34b655…2a6f
13 touches
27 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
12 touches
15 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity