pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,539,905
← previous block
next block →
recent activity
Analyzing
Block #90,539,905
7 transactions · 7 stateful · 2026-07-26 17:02:19 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,539,905
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39abec6b
#3
0x0f6795d9
· blocks 1
#5
setData
#6
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc5161979…e630
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x04da64b2…87f3
0x2ab50b…5c41
2 touches
0 conflicts
0x0849cefc…6a65
0x2ab50b…5c41
2 touches
0 conflicts
0x0bb94e8f…1e7e
0x2ab50b…5c41
2 touches
0 conflicts
0x0ec6d9ca…5526
0x2ab50b…5c41
2 touches
0 conflicts
0x1035ed1e…3885
0x2ab50b…5c41
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