pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,666,829
← previous block
next block →
recent activity
Analyzing
Block #74,666,829
17 transactions · 14 stateful · 2026-05-15 03:03:08 UTC
Parallelism
88
/100
Blocked
21
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,666,829
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#3
approve
#4
updatePrices
#5
0xed82b078
#6
0x6df9e92b
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xb30ef4…36a0
#11
0xfeeb31…fcce
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
· blocks 1
#2
execute
#7
0x6df9e92b
#16
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
15
w0
16
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xbec3bb74…7bb9
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xe84765…47bc
4 touches
1 conflict
0x00000000…0003
0xe84765…47bc
4 touches
1 conflict
0x00000000…0004
0xe84765…47bc
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
4 touches
1 conflict
0x76498d82…2995
0x000000…012a
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:
0xfdc9ea59…b68789
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity