← previous blocknext block →recent activity
Analyzing
Block #83,574,899
18 transactions · 13 stateful · 2026-06-25 09:38:27 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,574,899 · 18 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
1w04w17w09w010w111w212w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1e4de02…07e9
0x34b655…2a6f
4 touches
1 conflict
0xd9ad473c…92df
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x8e436347…96d0
0xd32edf…ff58
3 touches
1 conflict
0xaf51821e…291f
0x065c9d…c394
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
2 touches
0 conflicts
0x073918e2…b453
0x699abc…6a3b
2 touches
0 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
1 conflict on slot 0xd1e4de026f…2607e9
Audit this contract →
← previous block·next block →recent activity