pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,696,621
← previous block
next block →
recent activity
Analyzing
Block #94,696,621
10 transactions · 9 stateful · 2026-08-10 05:51:32 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,696,621
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x6ad2e98b
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#9
execOrders
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2d34e814…4baa
0x851145…3f07
4 touches
1 conflict
0x3198ab59…af3b
0x851145…3f07
4 touches
1 conflict
0xef05b756…d18f
0x851145…3f07
4 touches
1 conflict
0xa75c9396…11cf
0x851145…3f07
3 touches
1 conflict
0xc77e1533…2c34
0x851145…3f07
3 touches
1 conflict
0xb1a4d6b6…304f
0x01bff4…1071
2 touches
0 conflicts
0x703b861a…cbe3
0x188d58…ea8e
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:
0x851145ea…9f3f07
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity