pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,705,781
← previous block
next block →
recent activity
Analyzing
Block #73,705,781
10 transactions · 8 stateful · 2026-05-10 16:07:29 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,705,781
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
deposit
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
0xed82b078
#8
0x6a00adb8
#9
setData
#2
0xa09e9040
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
0x75a59900…5599
0x2a68ba…90c5
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ac31945…2c72
0x065c9d…c394
2 touches
0 conflicts
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x55fa8cc9…012c
0x2a68ba…90c5
2 touches
0 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
2 touches
0 conflicts
0xae69c125…2379
0x2a68ba…90c5
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: MarginAccount
1 conflict on slot
0x75a5990047…545599
Audit this contract →
← previous block
·
next block →
recent activity