pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,572,359
← previous block
next block →
recent activity
Analyzing
Block #93,572,359
11 transactions · 9 stateful · 2026-08-06 07:21:19 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,572,359
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x5acec890
#4
0x0f6795d9
#5
placeAndExecuteMarketSell
· blocks 2
#7
placeAndExecuteMarketSell
#8
0x3f5c179b
· blocks 1
#10
setData
#6
placeAndExecuteMarketBuy
· blocks 1
#9
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
8
w0
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x038a2197…d60d
0x851145…3f07
3 touches
1 conflict
0xb614c4a7…15f3
0x851145…3f07
3 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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:
0x01bff417…bc1071
1 conflict on slot
0x11b69a7ea1…83334e
Audit this contract →
← previous block
·
next block →
recent activity