← previous blocknext block →recent activity
Analyzing
Block #83,576,974
15 transactions · 14 stateful · 2026-06-25 09:52:16 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,576,974 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w09w111w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xe64e6363…e676
0x34b655…2a6f
6 touches
3 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
6 touches
3 conflicts
0x4467ecee…e95b
0x34b655…2a6f
5 touches
3 conflicts
0xc967cba9…5259
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
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
3 conflicts on slot 0x157dbfb216…8d4089
Audit this contract →
← previous block·next block →recent activity