← previous blocknext block →recent activity
Analyzing
Block #83,617,147
64 transactions · 41 stateful · 2026-06-25 14:20:26 UTC
Parallelism
72/100
Blocked
76%
Avg conflicts / tx
1.92
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,617,147 · 64 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
1w02w114w015w117w221w022w224w125w227w328w429w246w349w553w454w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0xa72c9dfd…a546
0xd32edf…ff58
11 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x75cdffd8…c217
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity