pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,228,982
← previous block
next block →
recent activity
Analyzing
Block #82,228,982
12 transactions · 8 stateful · 2026-06-19 03:46:58 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,228,982
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x57368ddf
#2
updateDataFeedsValuesPartial
#3
0x6a34bc29
#4
setData
#5
0x3cff3d…8e48
#6
0x8bdaa7…3d5a
#7
0xca26c8…f150
#8
redeemDelegations
#9
execOrders
· blocks 1
#10
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0xa369571c…1c3a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe3ce9025…da31
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x359fc107…551d
0x34b655…2a6f
4 touches
1 conflict
0x749437cf…2fc0
0xb754ba…508d
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
0x74fd0a9bd1…ea3aaa
Audit this contract →
← previous block
·
next block →
recent activity