pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,854,625
← previous block
next block →
recent activity
Analyzing
Block #93,854,625
12 transactions · 11 stateful · 2026-08-07 07:00:21 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,854,625
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcbbdb31a
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a7582fd
#9
setData
#10
0x39435dac
#11
0xc7e3ec2c
#4
0x0f6795d9
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
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22d93518…26d1
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5930
0x34b655…2a6f
2 touches
0 conflicts
0x42d5e8f3…5931
0x34b655…2a6f
2 touches
0 conflicts
0x47c24931…9b04
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
0x6d1b72eefe…416b78
Audit this contract →
← previous block
·
next block →
recent activity