pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,318,117
← previous block
next block →
recent activity
Analyzing
Block #94,318,117
10 transactions · 9 stateful · 2026-08-08 21:59:42 UTC
Parallelism
70
/100
Blocked
44
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,318,117
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#5
placeAndExecuteMarketBuy
· blocks 2
#9
setData
#4
0x0f6795d9
#6
placeAndExecuteMarketSell
· blocks 1
#8
0x0f6795d9
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
7
w2
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0xff9e45bf…99a0
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x0ad1fc8b…7516
0x34b655…2a6f
4 touches
1 conflict
0x7141ca79…8cf9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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:
Perpl
1 conflict on slot
0xf4db760d0a…f0fc5c
Audit this contract →
← previous block
·
next block →
recent activity