pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,271,556
← previous block
next block →
recent activity
Analyzing
Block #75,271,556
12 transactions · 11 stateful · 2026-05-17 22:21:42 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,271,556
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
0x0c7abd22
· blocks 1
#5
forward
#6
forward
#7
batchUpdate
#8
0xed82b078
#9
0x6a0a3fee
#10
setData
#11
execOrders
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x9a812987…c1f0
0xd32edf…ff58
3 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
2 touches
0 conflicts
0x2e3402ad…e443
0x754704…b603
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:
ShMonad (shMON)
1 conflict on slot
0xcb45d9d62a…b1cb84
Audit this contract →
← previous block
·
next block →
recent activity