pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,855,544
← previous block
next block →
recent activity
Analyzing
Block #72,855,544
7 transactions · 7 stateful · 2026-05-06 17:43:06 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,855,544
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6943a490
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xeffdedb0
#5
setData
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b8ffd61…f3ad
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
2 touches
0 conflicts
0xbf105daf…cab9
0x2185cd…21c7
2 touches
0 conflicts
0x8e47065d…3f30
0x2ae0cf…3d4e
2 touches
0 conflicts
0x8e47065d…3f35
0x2ae0cf…3d4e
2 touches
0 conflicts
0x8e47065d…3f36
0x2ae0cf…3d4e
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:
Perpl
1 conflict on slot
0x3b8ffd6160…92f3ad
Audit this contract →
← previous block
·
next block →
recent activity