← previous blocknext block →recent activity
Analyzing
Block #83,625,226
19 transactions · 16 stateful · 2026-06-25 15:14:26 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,625,226 · 19 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
1w02w13w07w08w19w212w113w014w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ed218ce…0548
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
0xbe1905a7…b8c7
0x34b655…2a6f
4 touches
1 conflict
0xc978dec7…e3d6
0x34b655…2a6f
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 0x1ed218ce18…180548
Audit this contract →
← previous block·next block →recent activity