pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,058,262
← previous block
next block →
recent activity
Analyzing
Block #94,058,262
8 transactions · 8 stateful · 2026-08-08 00:04:55 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,058,262
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
placeAndExecuteMarketSell
#2
0xd708c5d8
#3
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a76731e
#7
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x066768dd…a09c
0x037848…a1f7
2 touches
0 conflicts
0x066768dd…a09d
0x037848…a1f7
2 touches
0 conflicts
0x0eaa54cf…ce22
0x037848…a1f7
2 touches
0 conflicts
0x0eaa54cf…ce23
0x037848…a1f7
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:
Perpl
1 conflict on slot
0x8d5fc820e4…ea1750
Audit this contract →
← previous block
·
next block →
recent activity