← previous blocknext block →recent activity
Analyzing
Block #83,655,669
22 transactions · 19 stateful · 2026-06-25 18:37:44 UTC
Parallelism
73/100
Blocked
37%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,655,669 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w212w314w415w519w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
10 touches
10 conflicts
0xfefe55e0…32d4
0x34b655…2a6f
6 touches
3 conflicts
0x3e2c3d66…b580
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
6 touches
3 conflicts
0x78ae5f62…86ea
0x34b655…2a6f
6 touches
3 conflicts
0x7f9910cc…0f99
0x34b655…2a6f
6 touches
3 conflicts
0xa92c8763…6d7f
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 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity