← previous blocknext block →recent activity
Analyzing
Block #83,642,638
51 transactions · 44 stateful · 2026-06-25 17:10:47 UTC
Parallelism
55/100
Blocked
73%
Avg conflicts / tx
3.47
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #83,642,638 · 51 txs across 23 waves · depth 23
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w69w719w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x75cdffd8…c217
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
8 touches
6 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity