pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,299,983
← previous block
next block →
recent activity
Analyzing
Block #95,299,983
13 transactions · 10 stateful · 2026-08-12 08:38:03 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,299,983
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x325dd70c
· blocks 2
#3
updatePrices
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x94defb17
#7
updateDataFeedsValuesPartial
#8
0x6a7c3163
#9
setData
#10
execute
#12
0xb8024e95
#2
0xb414539a
#11
0x260595cf
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x66c70a3f…1e9c
0x754704…b603
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0xff393f19…4dd2
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0000
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…0002
0x0d73bf…be07
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:
0x63e48b72…8c53f2
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity