pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,981,543
← previous block
next block →
recent activity
Analyzing
Block #100,981,543
11 transactions · 11 stateful · 2026-09-01 07:23:21 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,981,543
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
· blocks 1
#4
transferWithAuthorization
#5
setData
#6
handleOps
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
0xed82b078
#10
0x6a967de1
#3
0x59558d29
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
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ab7447e…5333
0x000000…a032
2 touches
0 conflicts
0x0ca7395e…e360
0x000000…a032
2 touches
0 conflicts
0x21a5ce88…38fc
0x000000…a032
2 touches
0 conflicts
0x26022480…9dca
0x000000…a032
2 touches
0 conflicts
0x3a8e0c75…9a66
0x000000…a032
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004c
Audit this contract →
← previous block
·
next block →
recent activity