pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,626,481
← previous block
next block →
recent activity
Analyzing
Block #99,626,481
12 transactions · 12 stateful · 2026-08-27 13:33:24 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,626,481
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execOrder
#5
0x59558d29
#7
forward
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
setData
#11
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
0x2c24528e…0152
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xe957c63b…e347
0x851145…3f07
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
4 touches
1 conflict
0x326f09a5…4f49
0x851145…3f07
4 touches
1 conflict
0xd2b36119…e4e1
0x851145…3f07
4 touches
1 conflict
0x114dc7b7…b46b
0x851145…3f07
3 touches
1 conflict
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
0x2c24528e59…0f0152
Audit this contract →
← previous block
·
next block →
recent activity