← previous blocknext block →recent activity
Analyzing
Block #83,617,190
50 transactions · 46 stateful · 2026-06-25 14:20:43 UTC
Parallelism
66/100
Blocked
72%
Avg conflicts / tx
2.14
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,617,190 · 50 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
1w02w13w24w35w06w09w110w112w214w215w016w117w120w021w122w223w324w425w526w632w134w344w1246w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0xffc2f21e…b393
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0003
0x019883…2a9a
12 touches
15 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
12 touches
15 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x00000000…0002
0x019883…2a9a
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity