pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,025,650
← previous block
next block →
recent activity
Analyzing
Block #74,025,650
10 transactions · 8 stateful · 2026-05-12 03:48:32 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,025,650
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
0x6a02a387
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
forward
#8
0x6a02a387
#9
setData
#6
0xed82b078
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2e801a7d…32d9
0x065c9d…c394
2 touches
0 conflicts
0x328a22c5…67ac
0x065c9d…c394
2 touches
0 conflicts
0x5111b16b…bebc
0x065c9d…c394
2 touches
0 conflicts
0xdc52eabf…e4ff
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity