pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,893,366
← previous block
next block →
recent activity
Analyzing
Block #90,893,366
8 transactions · 7 stateful · 2026-07-27 22:40:36 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,893,366
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
reallocate
#2
0x0f6795d9
· blocks 1
#4
0x5339c59f
#5
updateDataFeedsValuesPartial
#6
setData
#7
0xef6ad1…45f5
#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
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0dfebe1d…6083
0x09475a…400f
2 touches
0 conflicts
0x741048ab…1e62
0x09475a…400f
2 touches
0 conflicts
0xee2e48fa…c427
0x09475a…400f
2 touches
0 conflicts
0xb25823d5…e4d9
0x754704…b603
2 touches
0 conflicts
0x0a7bc01e…73f1
0xd5d960…eaee
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