pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,898,774
← previous block
next block →
recent activity
Analyzing
Block #74,898,774
9 transactions · 6 stateful · 2026-05-16 04:51:10 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,898,774
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x053c0052
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x4e7eb462…b2ae
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x8e3143fb…2e8c
0xd32edf…ff58
3 touches
1 conflict
0x4b686cc4…bed8
0x065c9d…c394
2 touches
0 conflicts
0xb3d0b05b…e7b3
0x065c9d…c394
2 touches
0 conflicts
0xdce1361d…36d1
0x065c9d…c394
2 touches
0 conflicts
0xed6dd34e…5ec2
0x065c9d…c394
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
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity