pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,666,347
← previous block
next block →
recent activity
Analyzing
Block #74,666,347
17 transactions · 10 stateful · 2026-05-15 02:59:56 UTC
Parallelism
88
/100
Blocked
10
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,666,347
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#2
updatePrices
#4
updatePrices
#5
updatePrices
#6
0x1be2fb9c
#7
execPerpOps
#8
execPerpOps
#9
0x98717539
#10
0xed82b078
#11
updateDataFeedsValuesPartial
#12
setData
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x011fb8e3…054a
0x34b655…2a6f
2 touches
0 conflicts
0x016bd8f2…c85a
0x34b655…2a6f
2 touches
0 conflicts
0x0db61546…783d
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity