pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,571,910
← previous block
next block →
recent activity
Analyzing
Block #93,571,910
13 transactions · 12 stateful · 2026-08-06 07:19:04 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,571,910
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0x0f6795d9
#3
0x0f6795d9
#4
0x3f5c179b
#5
0x5339c59f
#6
updateDataFeedsValuesPartial
#7
0x6a7435df
#8
transfer
#9
0xe9316489
#10
setData
#12
0xc7e3ec2c
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71e1dee6…d11b
0x34b655…2a6f
4 touches
1 conflict
0xcfe07cff…a257
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x19486b00…ca10
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x26778400…177c
0x34b655…2a6f
2 touches
0 conflicts
0x2d541549…9cce
0x34b655…2a6f
2 touches
0 conflicts
0x42819a18…06b5
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
0x71e1dee6d7…5bd11b
Audit this contract →
← previous block
·
next block →
recent activity