← previous blocknext block →recent activity
Analyzing
Block #83,636,758
19 transactions · 18 stateful · 2026-06-25 16:31:31 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,636,758 · 19 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
3w04w18w29w311w212w114w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c320a0…b4a8
0x34b655…2a6f
8 touches
6 conflicts
0xf4b4898d…f948
0x34b655…2a6f
8 touches
6 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
6 touches
3 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf5970b31…f34c
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x948b9065…93b4
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 0x99c320a0a0…feb4a8
Audit this contract →
← previous block·next block →recent activity