pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,678,505
← previous block
next block →
recent activity
Analyzing
Block #90,678,505
9 transactions · 9 stateful · 2026-07-27 04:39:34 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,678,505
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98c6107a
· blocks 2
#4
updateDataFeedsValuesPartial
#5
transfer
#6
execFwdPositionOps
· blocks 1
#8
setData
#2
0x98c6107a
· blocks 1
#7
execFwdPositionOps
#3
0x98c6107a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd43be87…f667
0xe1c8b7…3022
6 touches
3 conflicts
0x44ed742f…63f5
0x3bd359…433a
6 touches
3 conflicts
0x4eb758b8…b13b
0x3bd359…433a
6 touches
3 conflicts
0xc6101b5d…4361
0x3bd359…433a
6 touches
3 conflicts
0x5504f74a…6874
0x43cf54…7777
6 touches
3 conflicts
0x00000000…0004
0x48c3bb…b17b
6 touches
3 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0xc824469a…6425
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:
0xe1c8b733…e33022
3 conflicts on slot
0xdd43be87b3…92f667
Audit this contract →
← previous block
·
next block →
recent activity