pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,980,427
← previous block
next block →
recent activity
Analyzing
Block #72,980,427
9 transactions · 8 stateful · 2026-05-07 07:34:15 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,980,427
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0xeffdedb0
#6
setData
#7
0x61633731
#8
0x39435dac
#2
0x0d484c28
· blocks 1
#3
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0xc361f873…4403
0xa6afd3…d132
3 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
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: MarginAccount
1 conflict on slot
0x8876d94c2a…cc8435
Audit this contract →
← previous block
·
next block →
recent activity