pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,635,114
← previous block
next block →
recent activity
Analyzing
Block #100,635,114
11 transactions · 11 stateful · 2026-08-31 02:20:20 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
#100,635,114
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
forward
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
0x3f5c179b
· blocks 1
#7
execFwdPositionOpsV2
#8
forward
#10
execOrders
#9
0xc7068c7b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xc545fdad…74de
0x851145…3f07
4 touches
1 conflict
0xce992a92…706e
0x851145…3f07
4 touches
1 conflict
0x352c45ab…a8ee
0x851145…3f07
4 touches
1 conflict
0x6a0638a3…fc78
0x851145…3f07
4 touches
1 conflict
0x6a5d686f…5ab8
0x851145…3f07
3 touches
1 conflict
0x32eb6ce1…7563
0x851145…3f07
3 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
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