← previous blocknext block →recent activity
Analyzing
Block #83,624,465
44 transactions · 38 stateful · 2026-06-25 15:09:23 UTC
Parallelism
57/100
Blocked
71%
Avg conflicts / tx
3.02
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,624,465 · 44 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w47w08w19w011w415w116w217w319w520w621w722w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x63c900f4…2600
0x34b655…2a6f
22 touches
55 conflicts
0x022f72c3…07b6
0xc8689a…ee79
20 touches
45 conflicts
0x4abf223d…0915
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x7322fb4a…635b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity