pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,224,632
← previous block
next block →
recent activity
Analyzing
Block #90,224,632
11 transactions · 10 stateful · 2026-07-25 14:21:19 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,224,632
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x1fe271b4
· blocks 1
#4
0x0f6795d9
#5
0x6a64c6d7
#6
transfer
· blocks 1
#8
setData
#9
0x39435dac
#10
0x39435dac
#3
0x1fe271b4
#7
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e72a4a7…3617
0x0a2fbf…29b1
4 touches
1 conflict
0x6e72a4a7…3618
0x0a2fbf…29b1
4 touches
1 conflict
0x6e72a4a7…361b
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0x6abb4f00…ce88
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0x6e72a4a762…293617
Audit this contract →
← previous block
·
next block →
recent activity