pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,201,501
← previous block
next block →
recent activity
Analyzing
Block #75,201,501
12 transactions · 12 stateful · 2026-05-17 14:33:24 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,201,501
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
transfer
#3
0x1ffa3c9b
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
forward
#8
0x6df9e92b
· blocks 1
#10
setData
#11
execOrders
#7
0xed82b078
#9
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22882eec…bc8a
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x81550c…bba7
4 touches
1 conflict
0x00000000…0001
0x81550c…bba7
4 touches
1 conflict
0x44ad89ba…cf83
0xb744f5…7777
4 touches
1 conflict
0x67813250…9467
0xb744f5…7777
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)
1 conflict on slot
0x22882eecec…28bc8a
Audit this contract →
← previous block
·
next block →
recent activity