pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,835,914
← previous block
next block →
recent activity
Analyzing
Block #90,835,914
12 transactions · 10 stateful · 2026-07-27 17:51:33 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,835,914
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
update
#2
executeMessage
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
0x0f6795d9
· blocks 1
#6
redeemDelegations
#7
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0x6a679b1d
#11
setData
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0x05d63043…be91
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x67a56c8b…f955
0x34b655…2a6f
2 touches
0 conflicts
0x7b67f6cf…0aab
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
0x85bfd0afba…f5ce96
Audit this contract →
← previous block
·
next block →
recent activity