pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,537,966
← previous block
next block →
recent activity
Analyzing
Block #90,537,966
10 transactions · 10 stateful · 2026-07-26 16:52:34 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,537,966
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#2
0xab083028
#3
0x5a5d9a99
#5
0x3f5c179b
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
transfer
#9
setData
#4
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee60d057…918f
0xfa32f9…f3f0
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
2 touches
0 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0005
0xfa32f9…f3f0
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:
0xfa32f9ec…fef3f0
1 conflict on slot
0xee60d0579b…a6918f
Audit this contract →
← previous block
·
next block →
recent activity