← previous blocknext block →recent activity
Analyzing
Block #83,483,430
20 transactions · 18 stateful · 2026-06-24 23:28:25 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,483,430 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w110w212w313w414w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6159d117…2e7e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x23475d41…6b10
0x34b655…2a6f
4 touches
1 conflict
0x78bf6d73…e990
0x34b655…2a6f
4 touches
1 conflict
0x8cf1f868…c5af
0x34b655…2a6f
4 touches
1 conflict
0x99ee776a…053a
0x34b655…2a6f
4 touches
1 conflict
0x9ff2b017…3fa2
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 0x6159d11796…9a2e7e
Audit this contract →
← previous block·next block →recent activity