← previous blocknext block →recent activity
Analyzing
Block #83,628,701
67 transactions · 52 stateful · 2026-06-25 15:37:41 UTC
Parallelism
70/100
Blocked
73%
Avg conflicts / tx
3.48
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,628,701 · 67 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w011w120w322w423w024w125w226w327w437w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…0002
0xaa7ee7…f0e4
24 touches
66 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
16 touches
28 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
12 touches
15 conflicts
0x5fad6fee…7714
0x34b655…2a6f
12 touches
15 conflicts
0xdb19247d…233c
0x34b655…2a6f
12 touches
15 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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity