pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,446,953
← previous block
next block →
recent activity
Analyzing
Block #90,446,953
12 transactions · 12 stateful · 2026-07-26 09:14:43 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,446,953
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5a5d9a99
· blocks 1
#3
0x785f5745
· blocks 1
#5
execFwdPositionOps
· blocks 1
#7
batchUpdate
#9
updateDataFeedsValuesPartial
#10
0x6a65d07a
#11
setData
#4
0x785f5745
#6
execFwdPositionOps
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc9cbb059…9e23
0x34b655…2a6f
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0002
0xbab229…9388
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
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:
0xbab2296c…069388
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity