pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,286,998
← previous block
next block →
recent activity
Analyzing
Block #90,286,998
9 transactions · 9 stateful · 2026-07-25 19:36:12 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,286,998
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a6510a4
#6
transfer
#7
setData
#8
0x39435dac
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9c46c042…90d8
0x34b655…2a6f
3 touches
1 conflict
0x0a3b8c54…1878
0x34b655…2a6f
2 touches
0 conflicts
0x0aaa3a0d…2343
0x34b655…2a6f
2 touches
0 conflicts
0x0aeef2b4…12cf
0x34b655…2a6f
2 touches
0 conflicts
0x167f697f…7f62
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity