pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,038,011
← previous block
next block →
recent activity
Analyzing
Block #73,038,011
7 transactions · 6 stateful · 2026-05-07 13:57:30 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,038,011
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x15ea9545
· blocks 1
#5
0xeffdedb0
#6
setData
#4
0x366fe5db
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
0x1728ed63…499c
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x1e1b2c44…f09a
0x065c9d…c394
2 touches
0 conflicts
0x7a75508f…fde3
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
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:
LeverUp: LeverUp
1 conflict on slot
0x1728ed6317…a9499c
Audit this contract →
← previous block
·
next block →
recent activity