← previous blocknext block →recent activity
Analyzing
Block #83,617,280
58 transactions · 42 stateful · 2026-06-25 14:21:19 UTC
Parallelism
72/100
Blocked
74%
Avg conflicts / tx
2.12
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,617,280 · 58 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w18w211w114w215w318w021w022w125w126w227w328w429w530w631w736w237w345w1248w455w1356w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
12 touches
15 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 conflicts
0x3f7ad3a0…de3b
0x34b655…2a6f
10 touches
10 conflicts
0x9af72ba2…f151
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0000
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0002
0x019883…2a9a
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity