pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,747,176
← previous block
next block →
recent activity
Analyzing
Block #89,747,176
9 transactions · 8 stateful · 2026-07-23 22:12:26 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,747,176
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6c05cd2b
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
bet
#7
setData
#8
0x7038ce…a1b1
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd80595db…0f52
0x11ed3b…2c96
2 touches
0 conflicts
0x00c46468…f328
0x3bd359…433a
2 touches
0 conflicts
0x4c770fe0…b972
0x3bd359…433a
2 touches
0 conflicts
0xb4e825af…69e0
0x3bd359…433a
2 touches
0 conflicts
0xfbe161dd…757b
0x3bd359…433a
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity