pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,287,803
← previous block
next block →
recent activity
Analyzing
Block #90,287,803
10 transactions · 10 stateful · 2026-07-25 19:40:17 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,287,803
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#5
executeBatch
#6
0x6a651199
#7
setData
#8
0x39435dac
· blocks 1
#4
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5474fcb…e081
0x34b655…2a6f
4 touches
1 conflict
0x0444f178…8568
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f82dba2…24d6
0x34b655…2a6f
4 touches
1 conflict
0xc4ca986e…4e06
0x34b655…2a6f
3 touches
1 conflict
0x330df1e6…7587
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
0xd5474fcbb1…1ce081
Audit this contract →
← previous block
·
next block →
recent activity