← previous blocknext block →recent activity
Analyzing
Block #83,452,740
14 transactions · 11 stateful · 2026-06-24 20:03:35 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,452,740 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w19w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f2f9e67…3be0
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb6c88e49…7bbf
0x34b655…2a6f
4 touches
1 conflict
0xba083667…24cb
0xd32edf…ff58
3 touches
1 conflict
0x7ccfaa3d…467f
0x34b655…2a6f
2 touches
0 conflicts
0x7cea42e1…e57a
0x34b655…2a6f
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 0x8f2f9e67ec…4f3be0
Audit this contract →
← previous block·next block →recent activity