pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,720,850
← previous block
next block →
recent activity
Analyzing
Block #90,720,850
11 transactions · 10 stateful · 2026-07-27 08:12:35 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,720,850
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x5a5d9a99
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
setData
#9
0x39435dac
#10
0xc7e3ec2c
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x12987f9e…1a57
0x34b655…2a6f
2 touches
0 conflicts
0x36ce9a1f…645f
0x34b655…2a6f
2 touches
0 conflicts
0x41cff9d2…f332
0x34b655…2a6f
2 touches
0 conflicts
0x48e3acd8…cf41
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:
0x48cba278…e2b48b
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity