pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,418,161
← previous block
next block →
recent activity
Analyzing
Block #73,418,161
8 transactions · 7 stateful · 2026-05-09 08:06:53 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,418,161
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#6
setData
#5
0x98717539
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8240d70c…7c3b
0x34b655…2a6f
4 touches
1 conflict
0x9ea57326…329f
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ae
0x8d66a4…3095
4 touches
1 conflict
0xfff38d9f…7063
0x8d66a4…3095
4 touches
1 conflict
0x1db301a1…dda1
0x34b655…2a6f
2 touches
0 conflicts
0x20d070c8…c414
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x9ddd1b34…3f04
0x34b655…2a6f
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
0x8240d70c8a…f27c3b
Audit this contract →
← previous block
·
next block →
recent activity