pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,022,493
← previous block
next block →
recent activity
Analyzing
Block #74,022,493
13 transactions · 10 stateful · 2026-05-12 03:27:31 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,022,493
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
transfer
· blocks 1
#3
transfer
#5
execPerpOps
#6
execPerpOps
#7
handleOps
#8
updateDataFeedsValuesPartial
#9
batchUpdate
#10
0xed82b078
#11
0xed82b078
#12
setData
#4
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4058df36…481a
0x065c9d…c394
2 touches
0 conflicts
0x51d7a14e…8eb0
0x065c9d…c394
2 touches
0 conflicts
0x6852cb1d…c969
0x065c9d…c394
2 touches
0 conflicts
0xba794da8…8336
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:
0xe7cd86e1…0fc82d
1 conflict on slot
0xc4e19ae47e…dc0788
Audit this contract →
← previous block
·
next block →
recent activity