← previous blocknext block →recent activity
Analyzing
Block #83,632,321
10 transactions · 9 stateful · 2026-06-25 16:01:51 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,632,321 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1da6b83a…87e0
0x34b655…2a6f
4 touches
1 conflict
0xa57576bb…e01f
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x1e346a85…e9c5
0x34b655…2a6f
4 touches
1 conflict
0x0ba3469f…0a48
0x34b655…2a6f
2 touches
0 conflicts
0x1202acc8…77d0
0x34b655…2a6f
2 touches
0 conflicts
0x54ff7a67…5bf8
0x34b655…2a6f
2 touches
0 conflicts
0x60f64a33…701f
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 0x1da6b83afb…f287e0
Audit this contract →
← previous block·next block →recent activity