← previous blocknext block →recent activity
Analyzing
Block #83,412,001
27 transactions · 23 stateful · 2026-06-24 15:31:27 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,412,001 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w413w418w219w324w426w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbec4dcb…832e
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x5d2b5661…df66
0x34b655…2a6f
6 touches
3 conflicts
0x604d1daf…bf48
0x34b655…2a6f
6 touches
3 conflicts
0xb4ed1624…ab5f
0x34b655…2a6f
6 touches
3 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xbbec4dcb3d…35832e
Audit this contract →
← previous block·next block →recent activity