← previous blocknext block →recent activity
Analyzing
Block #83,876,301
66 transactions · 47 stateful · 2026-06-26 19:09:48 UTC
Parallelism
67/100
Blocked
74%
Avg conflicts / tx
3.38
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #83,876,301 · 66 txs across 22 waves · depth 22
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
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w216w317w419w520w622w723w825w948w1049w1152w953w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3975d93…b4a2
0x34b655…2a6f
30 touches
105 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0xe02484a6…c32e
0xc8689a…ee79
26 touches
78 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
26 touches
78 conflicts
0x8726ff39…3be8
0x34b655…2a6f
26 touches
78 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 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
105 conflicts on slot 0xb3975d9364…28b4a2
Audit this contract →
← previous block·next block →recent activity