pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,687,453
← previous block
next block →
recent activity
Analyzing
Block #73,687,453
11 transactions · 10 stateful · 2026-05-10 14:03:52 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,687,453
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcf7468f4
#2
0x39ecce49
· blocks 2
#5
0x42dd8743
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x0c7abd22
#9
0x6a0090bf
#10
setData
#3
0x39ecce49
· blocks 1
#8
0x62be7533
#4
0x39ecce49
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4b00f4b…34c0
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x3e1523…94aa
6 touches
3 conflicts
0x00000000…0001
0x3e1523…94aa
6 touches
3 conflicts
0x00000000…0003
0x3e1523…94aa
6 touches
3 conflicts
0xed385e36…0251
0x7b2728…7777
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xae69c125…2379
0x2a68ba…90c5
4 touches
1 conflict
0x6d27debc…839b
0x065c9d…c394
4 touches
1 conflict
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:
Wrapped MON (WMON)
3 conflicts on slot
0xe4b00f4b11…9234c0
Audit this contract →
← previous block
·
next block →
recent activity