pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,971,109
← previous block
next block →
recent activity
Analyzing
Block #94,971,109
8 transactions · 8 stateful · 2026-08-11 04:53:40 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,971,109
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
placeAndExecuteMarketBuy
· blocks 2
#6
updateDataFeedsValuesPartial
#7
setData
#4
placeAndExecuteMarketSell
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf9312173…41a7
0x851145…3f07
4 touches
1 conflict
0x23d51e55…82c2
0x34b655…2a6f
2 touches
0 conflicts
0x353d5b89…a4d7
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
0x34b655…2a6f
2 touches
0 conflicts
0x8590b692…b267
0x34b655…2a6f
2 touches
0 conflicts
0x8bc5abbb…a84e
0x34b655…2a6f
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