← previous blocknext block →recent activity
Analyzing
Block #83,465,635
10 transactions · 9 stateful · 2026-06-24 21:29:46 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,465,635 · 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
2w04w15w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x1a9bae76…9eb3
0x065c9d…c394
4 touches
1 conflict
0xbcc61e41…0c1c
0x065c9d…c394
3 touches
1 conflict
0x5881a35f…0518
0x065c9d…c394
3 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x6fabd21d…6d3b
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0xec938aa9…cb15
0x065c9d…c394
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 0x8b305a3b6b…0c1c35
Audit this contract →
← previous block·next block →recent activity