pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,699,159
← previous block
next block →
recent activity
Analyzing
Block #100,699,159
13 transactions · 12 stateful · 2026-08-31 07:42:29 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,699,159
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
setPrice
#3
setPrice
#4
setPrice
#5
updatePrices
· blocks 1
#7
0x59558d29
#8
0x41a8f47c
#9
placeAndExecuteMarketBuy
#10
transfer
#11
setData
#12
0xc7068c7b
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x2b36ecc6…093e
0x3c2269…cf62
2 touches
0 conflicts
0x7a814f0d…35fd
0x3c2269…cf62
2 touches
0 conflicts
0xe7f4dbde…a996
0x3c2269…cf62
2 touches
0 conflicts
0x3040553c…5e28
0x754704…b603
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