pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,475,966
← previous block
next block →
recent activity
Analyzing
Block #74,475,966
9 transactions · 8 stateful · 2026-05-14 05:44:15 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,475,966
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x785f5745
#5
executeOrders
#6
redeemDelegations
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38dee07f…7598
0x34b655…2a6f
4 touches
1 conflict
0xab621973…cc16
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0008
0x06fc8b…c6b4
2 touches
0 conflicts
0x0a74ccfe…774e
0x06fc8b…c6b4
2 touches
0 conflicts
0x18086d47…eb75
0x06fc8b…c6b4
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0x4c1c03db…93c4
0x0c65a0…0852
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
0x38dee07f65…c77598
Audit this contract →
← previous block
·
next block →
recent activity