← previous blocknext block →recent activity
Analyzing
Block #83,668,364
19 transactions · 17 stateful · 2026-06-25 20:02:22 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,668,364 · 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
3w04w15w28w010w113w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2754e960…bcc1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xec85756f…0ba2
0x34b655…2a6f
8 touches
6 conflicts
0x9ec861cc…36c8
0x34b655…2a6f
6 touches
3 conflicts
0x68c6b2fa…098d
0x34b655…2a6f
5 touches
3 conflicts
0x32229dd3…4dbb
0x34b655…2a6f
5 touches
3 conflicts
0x4e1ce17e…98a7
0x34b655…2a6f
4 touches
1 conflict
0x528a1d82…6485
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 0x2754e96062…21bcc1
Audit this contract →
← previous block·next block →recent activity