pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,227,511
← previous block
next block →
recent activity
Analyzing
Block #82,227,511
14 transactions · 12 stateful · 2026-06-19 03:37:08 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,227,511
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
0xed82b078
#3
updatePrices
#4
redeemDelegations
· blocks 1
#5
0x0f6795d9
#6
0x0f6795d9
#7
0x2993270a
#8
0x6a34b9dc
#9
setData
#10
0x761bf4…8a23
#12
0x39435dac
#13
0x39435dac
#11
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x31bab6…b42a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0x2e7a0c1d…caaf
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0xd8f0bddf…a548
0x34b655…2a6f
2 touches
0 conflicts
0xd8f0bddf…a549
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:
0x31bab6c9…16b42a
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity