pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,438,501
← previous block
next block →
recent activity
Analyzing
Block #93,438,501
8 transactions · 8 stateful · 2026-08-05 20:08:25 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,438,501
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
setData
#7
0xc7e3ec2c
#4
0x0f6795d9
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86c98782…f3b7
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xf18f246b…fdbc
0x34b655…2a6f
4 touches
1 conflict
0x04ac0426…5960
0x34b655…2a6f
2 touches
0 conflicts
0x12c7de30…7aa8
0x34b655…2a6f
2 touches
0 conflicts
0x154b4443…bc47
0x34b655…2a6f
2 touches
0 conflicts
0x1f00a5b3…bf76
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
0x86c98782f1…e7f3b7
Audit this contract →
← previous block
·
next block →
recent activity