← previous blocknext block →recent activity
Analyzing
Block #83,356,130
11 transactions · 10 stateful · 2026-06-24 09:18:04 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,356,130 · 11 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
1w02w13w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xf8372997…869e
0x34b655…2a6f
6 touches
3 conflicts
0x0d35e1ad…b4d6
0x34b655…2a6f
6 touches
3 conflicts
0x18cbab19…7a73
0x34b655…2a6f
4 touches
1 conflict
0x23c16bab…1018
0x34b655…2a6f
4 touches
1 conflict
0x2c0629ae…9745
0x34b655…2a6f
4 touches
1 conflict
0x5d2b5661…df66
0x34b655…2a6f
4 touches
1 conflict
0x5f708d0c…1c2c
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity