pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,720,355
← previous block
next block →
recent activity
Analyzing
Block #90,720,355
9 transactions · 9 stateful · 2026-07-27 08:10:06 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,720,355
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#2
0x3f5c179b
#4
forward
#5
updateDataFeedsValuesPartial
#6
setData
#8
0xc7e3ec2c
#3
0x0f6795d9
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10379e8d…3675
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x917f99a5…7989
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0xbb322930…ace5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x06c980ab…5577
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
0x10379e8db9…2b3675
Audit this contract →
← previous block
·
next block →
recent activity