← previous blocknext block →recent activity
Analyzing
Block #83,617,654
51 transactions · 31 stateful · 2026-06-25 14:23:49 UTC
Parallelism
69/100
Blocked
68%
Avg conflicts / tx
2.63
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,617,654 · 51 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w110w112w213w318w119w220w321w422w523w624w725w826w927w1028w1129w1230w1331w1432w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0xa51c97e1…6b55
0x34b655…2a6f
10 touches
10 conflicts
0xaa6f28d9…83ef
0x34b655…2a6f
10 touches
10 conflicts
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity