pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,458,688
← previous block
next block →
recent activity
Analyzing
Block #90,458,688
9 transactions · 9 stateful · 2026-07-26 10:13:44 UTC
Parallelism
56
/100
Blocked
44
%
Avg conflicts / tx
0.56
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,458,688
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 1
#4
0x0f6795d9
#6
setData
· blocks 1
#3
0x0f6795d9
· blocks 2
#7
setData
#5
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
6
w0
7
w1
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x43915ca6…bd77
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x248241b8…7e99
0x34b655…2a6f
2 touches
0 conflicts
0x262d4253…b091
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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
3 conflicts on slot
0x4c18893450…c5158e
Audit this contract →
← previous block
·
next block →
recent activity