pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,871,318
← previous block
next block →
recent activity
Analyzing
Block #89,871,318
8 transactions · 5 stateful · 2026-07-24 08:38:35 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,871,318
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
0x1fe271b4
· blocks 1
#4
0x1fe271b4
#5
0x1fe271b4
#7
setData
#6
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x347317f9…7937
0x0a2fbf…29b1
4 touches
1 conflict
0x347317f9…7938
0x0a2fbf…29b1
4 touches
1 conflict
0x9055352a…a6c6
0x0a2fbf…29b1
4 touches
1 conflict
0x9055352a…a6c7
0x0a2fbf…29b1
4 touches
1 conflict
0x9055352a…a6ca
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0xd8560627…fd7e
0x370e2e…63b4
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
0x347317f98d…757937
Audit this contract →
← previous block
·
next block →
recent activity