← previous blocknext block →recent activity
Analyzing
Block #83,655,614
64 transactions · 46 stateful · 2026-06-25 18:37:21 UTC
Parallelism
70/100
Blocked
80%
Avg conflicts / tx
3.92
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,655,614 · 64 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w09w110w211w312w413w514w615w716w817w951w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
38 touches
171 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0xd064a456…b881
0x34b655…2a6f
18 touches
36 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
16 touches
28 conflicts
0x487922c6…dbd2
0x34b655…2a6f
16 touches
28 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0x22e0cc1d…ad0d
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
171 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity