pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,018,833
← previous block
next block →
recent activity
Analyzing
Block #82,018,833
15 transactions · 9 stateful · 2026-06-18 04:25:34 UTC
Parallelism
87
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,018,833
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
execOrders
#4
execOrders
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x5a5d9a99
#9
executeBatch
#10
0x57368ddf
#11
execute
· blocks 1
#13
0xb36199…fdea
#14
setData
#12
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x24b18e…3301
4 touches
1 conflict
0x797464db…e15a
0x788571…8888
4 touches
1 conflict
0xa743c8dd…ebf2
0x788571…8888
4 touches
1 conflict
0x771a3650…01cd
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x24b18e…3301
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
2 touches
0 conflicts
0x5149ba0e…d954
0x754704…b603
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:
0x24b18eb6…733301
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity