pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,531,181
← previous block
next block →
recent activity
Analyzing
Block #90,531,181
9 transactions · 9 stateful · 2026-07-26 16:18:26 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,531,181
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 3
#4
0x0f6795d9
#7
setData
#5
0x0f6795d9
· blocks 1
#8
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2b8d9898…d525
0x34b655…2a6f
4 touches
1 conflict
0x0572078b…a210
0x34b655…2a6f
2 touches
0 conflicts
0x06db8daf…5718
0x34b655…2a6f
2 touches
0 conflicts
0x06df379f…2653
0x34b655…2a6f
2 touches
0 conflicts
0x0b637a19…4f72
0x34b655…2a6f
2 touches
0 conflicts
0x14c4e3ca…edd9
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
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity