pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,978,683
← previous block
next block →
recent activity
Analyzing
Block #90,978,683
13 transactions · 13 stateful · 2026-07-28 05:49:46 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,978,683
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
commitVerification
#2
0x5a5d9a99
#3
executeBatch
#4
0x3f5c179b
#5
0x0f6795d9
#6
commit
#7
0x39435dac
· blocks 1
#9
0x6a684372
#10
setData
#11
0x39435dac
#12
0xc7e3ec2c
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x705ab4ae…0162
0x34b655…2a6f
4 touches
1 conflict
0x57fe9270…88a5
0x34b655…2a6f
4 touches
1 conflict
0xdecb94d5…606f
0x34b655…2a6f
3 touches
1 conflict
0xfcaee83d…428d
0x34b655…2a6f
2 touches
0 conflicts
0x1716b13d…99cc
0xc8689a…ee79
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity