← previous blocknext block →recent activity
Analyzing
Block #83,629,629
13 transactions · 9 stateful · 2026-06-25 15:43:52 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,629,629 · 13 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
4w07w08w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d3317b2…4f2a
0x34b655…2a6f
8 touches
6 conflicts
0xa1e51cc8…e4cf
0x34b655…2a6f
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xff4ee2c4…6e5e
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x37a276a3…673f
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
6 conflicts on slot 0x0d3317b2dc…6d4f2a
Audit this contract →
← previous block·next block →recent activity