← previous blocknext block →recent activity
Analyzing
Block #83,758,338
37 transactions · 34 stateful · 2026-06-26 06:02:35 UTC
Parallelism
51/100
Blocked
59%
Avg conflicts / tx
3.57
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,758,338 · 37 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w09w110w211w312w413w514w615w717w818w919w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0x326a02b5…8dad
0x34b655…2a6f
16 touches
28 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
14 touches
21 conflicts
0x213a54fa…c85f
0x34b655…2a6f
12 touches
20 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0xd12ab8ed…505a
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity