← previous blocknext block →recent activity
Analyzing
Block #83,624,457
25 transactions · 24 stateful · 2026-06-25 15:09:20 UTC
Parallelism
32/100
Blocked
67%
Avg conflicts / tx
5.32
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,624,457 · 25 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w710w811w912w1013w1114w1220w1321w1422w1523w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
32 touches
120 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0x022f72c3…07b6
0xc8689a…ee79
24 touches
66 conflicts
0x63c900f4…2600
0x34b655…2a6f
24 touches
66 conflicts
0xffc2f21e…b393
0x34b655…2a6f
24 touches
66 conflicts
0x4abf223d…0915
0x34b655…2a6f
22 touches
57 conflicts
0xee7978e9…2869
0x34b655…2a6f
11 touches
27 conflicts
0x326a02b5…8dad
0x34b655…2a6f
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity