pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,638,791
← previous block
next block →
recent activity
Analyzing
Block #90,638,791
11 transactions · 10 stateful · 2026-07-27 01:19:47 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,638,791
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
withdraw
#3
0x0f6795d9
· blocks 2
#4
0x0f6795d9
#6
0x3f5c179b
#7
0x3f5c179b
#9
setData
#10
0x39435dac
#5
0x0f6795d9
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b90997…cf6b
0x34b655…2a6f
4 touches
1 conflict
0x071163fa…f7db
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x0fe1e6e0…f553
0x34b655…2a6f
2 touches
0 conflicts
0x18e86f02…fa98
0x34b655…2a6f
2 touches
0 conflicts
0x1bd6ddeb…9a19
0x34b655…2a6f
2 touches
0 conflicts
0x2132931c…59f7
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
0x20b90997d0…a4cf6b
Audit this contract →
← previous block
·
next block →
recent activity