← previous blocknext block →recent activity
Analyzing
Block #83,638,929
39 transactions · 33 stateful · 2026-06-25 16:46:01 UTC
Parallelism
62/100
Blocked
61%
Avg conflicts / tx
2.64
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,638,929 · 39 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w28w314w015w117w018w119w220w321w422w523w624w725w826w927w1028w1129w1230w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0x1b1df992…40eb
0x34b655…2a6f
16 touches
28 conflicts
0xf324b405…ca30
0x34b655…2a6f
16 touches
28 conflicts
0x157dbfb2…4089
0x34b655…2a6f
12 touches
15 conflicts
0xe64e6363…e676
0x34b655…2a6f
11 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
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity