pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,019,056
← previous block
next block →
recent activity
Analyzing
Block #82,019,056
24 transactions · 15 stateful · 2026-06-18 04:27:03 UTC
Parallelism
79
/100
Blocked
47
%
Avg conflicts / tx
0.42
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,019,056
· 24 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
batchUpdate
· blocks 2
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
execFwdPositionOps
· blocks 2
#9
execFwdPositionOps
#10
relay
#11
0x3f5c179b
#12
updateDataFeedsValuesPartial
#13
updateDataFeedsValuesPartial
#14
0xe9316489
#15
0xa94a3f…2076
#16
0xc0d9ae…4fe4
#17
0x517bf7…7cb6
#18
0xc64364…d4e4
#19
setData
#21
execOrders
#2
0xed82b078
· blocks 1
#20
execOrders
· blocks 2
#3
0xed82b078
· blocks 1
#22
execOrders
· blocks 1
#4
addBuyOrder
· blocks 1
#23
execOrders
#5
batchCancelOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
8
w0
20
w1
22
w2
23
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x38d0f220…01f4
0x34b655…2a6f
4 touches
1 conflict
0x6100906b…8421
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity