pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,804,117
← previous block
next block →
recent activity
Analyzing
Block #104,804,117
15 transactions · 12 stateful · 2026-09-14 17:14:45 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,804,117
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
· blocks 1
#3
updatePrices
#5
0xab083028
#6
execOrder
#7
0x5acec890
#8
0x59558d29
#9
execPerpOps
#10
execPerpOps
#11
setData
#12
0x6aa82b89
#13
execOrders
#14
execOrders
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1950c0ce…09e3
0x754704…b603
2 touches
0 conflicts
0x2520e31b…6ffd
0x754704…b603
2 touches
0 conflicts
0x2633438b…8c3a
0x754704…b603
2 touches
0 conflicts
0x209b5362…d335
0x99c7a7…8bf0
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:
0xf5b5f7f8…a36d70
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity