← previous blocknext block →recent activity
Analyzing
Block #83,655,225
50 transactions · 37 stateful · 2026-06-25 18:34:45 UTC
Parallelism
60/100
Blocked
73%
Avg conflicts / tx
3.16
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,655,225 · 50 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w29w310w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x975680c7…0e39
0xa6afd3…d132
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
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity