pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,892,425
← previous block
next block →
recent activity
Analyzing
Block #91,892,425
14 transactions · 13 stateful · 2026-07-31 10:29:50 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,892,425
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
transfer
· blocks 1
#5
0x5a5d9a99
#6
0x5a5d9a99
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
#9
0x0f6795d9
#10
0x0f6795d9
#11
setData
#12
0x59558d29
#13
0xc7e3ec2c
#4
transfer
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
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
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
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