pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,971,755
← previous block
next block →
recent activity
Analyzing
Block #94,971,755
15 transactions · 12 stateful · 2026-08-11 04:56:54 UTC
Parallelism
87
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,971,755
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
updatePrices
#3
0x94defb17
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
· blocks 1
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#14
execOrders
#4
0x94defb17
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2e94867…cfd1
0x968279…9342
4 touches
1 conflict
0xb2e94867…cfd4
0x968279…9342
4 touches
1 conflict
0xb2e94867…cfd5
0x968279…9342
4 touches
1 conflict
0xb2e94867…cfd7
0x968279…9342
4 touches
1 conflict
0xef5dc580…ca50
0x968279…9342
4 touches
1 conflict
0xef5dc580…ca51
0x968279…9342
4 touches
1 conflict
0xef5dc580…ca53
0x968279…9342
4 touches
1 conflict
0xe181f491…f4e3
0x34b655…2a6f
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:
0x96827978…f09342
1 conflict on slot
0xb2e9486754…15cfd1
Audit this contract →
← previous block
·
next block →
recent activity