pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,795,949
← previous block
next block →
recent activity
Analyzing
Block #94,795,949
14 transactions · 14 stateful · 2026-08-10 14:12:37 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,795,949
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x29eed2d3
#4
0x94defb17
· blocks 1
#6
forward
#7
setData
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#5
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc4f5130…5fea
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xbf85b0c2…d70e
0x968279…9342
4 touches
1 conflict
0xbf85b0c2…d70f
0x968279…9342
4 touches
1 conflict
0xbf85b0c2…d711
0x968279…9342
4 touches
1 conflict
0xfc4f5130…5fe3
0x968279…9342
4 touches
1 conflict
0xfc4f5130…5fe4
0x968279…9342
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
0xfc4f5130f3…545fea
Audit this contract →
← previous block
·
next block →
recent activity