← previous blocknext block →recent activity
Analyzing
Block #83,637,670
19 transactions · 17 stateful · 2026-06-25 16:37:37 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,637,670 · 19 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
1w02w13w24w05w16w07w28w313w015w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ac79c76…c4a9
0x34b655…2a6f
10 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x619f5683…5bd4
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x68ff0855…356c
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
10 conflicts on slot 0x9ac79c76e2…88c4a9
Audit this contract →
← previous block·next block →recent activity