pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,021,117
← previous block
next block →
recent activity
Analyzing
Block #101,021,117
10 transactions · 8 stateful · 2026-09-01 10:42:31 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,021,117
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67098489
#2
0xab083028
· blocks 1
#4
forward
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
executeBatch
#9
0x6a96ac8e
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x00fcb08e…5bbf
0x34b655…2a6f
2 touches
0 conflicts
0x054a93cb…cbef
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x34ae4d08…a73fc5
1 conflict on slot
0xa605468c6d…6d1bfc
Audit this contract →
← previous block
·
next block →
recent activity