pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,957,339
← previous block
next block →
recent activity
Analyzing
Block #91,957,339
11 transactions · 11 stateful · 2026-07-31 15:56:22 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,957,339
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#5
0x39435dac
#6
0x0f6795d9
#7
0x6a6cc61d
#8
setData
#9
0x39435dac
#10
0x59558d29
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
2 touches
0 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
2 touches
0 conflicts
0x3111a64f…eb7f
0x34b655…2a6f
2 touches
0 conflicts
0x38fd4b63…4222
0x34b655…2a6f
2 touches
0 conflicts
0x3915423d…7a97
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x8ec95f2b0e…b0f4d7
Audit this contract →
← previous block
·
next block →
recent activity