pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,839,426
← previous block
next block →
recent activity
Analyzing
Block #94,839,426
11 transactions · 10 stateful · 2026-08-10 17:51:20 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,839,426
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#6
executeBatch
· blocks 1
#8
0x6a7a1010
#9
setData
#10
execOrders
#7
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x778706bb…231e
0xe52b14…7230
3 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x45b4ae9c…dcf4
0x34b655…2a6f
2 touches
0 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
2 touches
0 conflicts
0xbba9fb9c…dad5
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
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:
0xe52b1424…bb7230
1 conflict on slot
0x0b0c2e8d5e…dbc1b8
Audit this contract →
← previous block
·
next block →
recent activity