pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,606,385
← previous block
next block →
recent activity
Analyzing
Block #74,606,385
10 transactions · 6 stateful · 2026-05-14 20:19:57 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,606,385
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#3
0xed82b078
#4
updateDataFeedsValuesPartial
#5
transfer
#6
setData
#7
0x4da67e…22f3
#8
0x059ffe…bf9d
#9
0xf1a3bf…ff1d
#2
0x1ffa3c9b
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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x14e7a80c…6c99
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x2b397b26…724b
0x065c9d…c394
2 touches
0 conflicts
0x6ad750f1…5a64
0x065c9d…c394
2 touches
0 conflicts
0x72f54a3b…925b
0x065c9d…c394
2 touches
0 conflicts
0x79e8fcd5…9bde
0x065c9d…c394
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity