← previous blocknext block →recent activity
Analyzing
Block #83,652,938
13 transactions · 11 stateful · 2026-06-25 18:19:34 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,652,938 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0x0260a33f…9169
0x065c9d…c394
2 touches
0 conflicts
0xc3816ff3…e632
0x065c9d…c394
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x165b73ba…7c99
0x34b655…2a6f
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity