pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,650,345
← previous block
next block →
recent activity
Analyzing
Block #74,650,345
11 transactions · 10 stateful · 2026-05-15 01:12:49 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,650,345
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x1ffa3c9b
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6df9e92b
#6
addLiquidity
#7
0xc5a04723
#8
setData
#9
0x39435dac
#10
0x053c0052
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x76a6acbd…573c
0x065c9d…c394
3 touches
1 conflict
0x92989da3…e23b
0x065c9d…c394
3 touches
1 conflict
0x2ff6968d…7e43
0x065c9d…c394
2 touches
0 conflicts
0x35b1dc2f…2f44
0x065c9d…c394
2 touches
0 conflicts
0x9f7a2132…643b
0x065c9d…c394
2 touches
0 conflicts
0xc5299629…5df0
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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