pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,579,408
← previous block
next block →
recent activity
Analyzing
Block #89,579,408
10 transactions · 8 stateful · 2026-07-23 05:58:36 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,579,408
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
0x1fe271b4
· blocks 1
#8
0x5339c59f
#9
setData
#4
0x0f6795d9
#7
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc0c65c4…7ece
0x0a2fbf…29b1
4 touches
1 conflict
0xeac0c96e…b7fb
0x0a2fbf…29b1
4 touches
1 conflict
0xeac0c96e…b7fc
0x0a2fbf…29b1
4 touches
1 conflict
0xeac0c96e…b7ff
0x0a2fbf…29b1
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0x0f56b167…5159
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
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
0xbc0c65c443…b17ece
Audit this contract →
← previous block
·
next block →
recent activity