pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,263,413
← previous block
next block →
recent activity
Analyzing
Block #99,263,413
11 transactions · 11 stateful · 2026-08-26 06:58:43 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,263,413
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
0x928e4afa
#5
0x59558d29
#7
batchUpdate
#8
0x6a8e8f1b
#9
setData
#10
execOrders
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5092059d…81ff
0x851145…3f07
4 touches
1 conflict
0xe3ebb524…e9da
0x851145…3f07
4 touches
1 conflict
0xeffd747c…6a01
0x851145…3f07
4 touches
1 conflict
0x46c719fb…61df
0x851145…3f07
3 touches
1 conflict
0x4c86efac…1859
0x851145…3f07
3 touches
1 conflict
0x12f129f2…fe6b
0x2b46c0…1669
2 touches
0 conflicts
0x260cc5c4…bef0
0x2b46c0…1669
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