pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,355,718
← previous block
next block →
recent activity
Analyzing
Block #74,355,718
13 transactions · 10 stateful · 2026-05-13 16:23:53 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,355,718
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
flash
#4
get_block_hash_257335279069929
#5
0x5bf9264c
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#8
redeemDelegations
#9
0xed82b078
#10
0x5339c59f
#11
0x6a04a611
#12
setData
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c98636a…bab1
0xde22b2…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0001
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0005
0x354d92…66fb
2 touches
0 conflicts
0xac33ff75…077b
0x354d92…66fb
2 touches
0 conflicts
0x76f2524a…306c
0x3bd359…433a
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:
0xde22b2d5…9f7777
1 conflict on slot
0x1c98636a2f…f3bab1
Audit this contract →
← previous block
·
next block →
recent activity