← previous blocknext block →recent activity
Analyzing
Block #83,638,113
19 transactions · 18 stateful · 2026-06-25 16:40:35 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,638,113 · 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
1w02w13w24w06w07w18w29w311w314w416w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44843215…109b
0x34b655…2a6f
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xdb95e18e…c73a
0x1b6862…e19c
6 touches
3 conflicts
0x18f3cbb0…1b55
0x34b655…2a6f
6 touches
3 conflicts
0x1ec45a88…c8c6
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x44843215c9…be109b
Audit this contract →
← previous block·next block →recent activity