pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,986,020
← previous block
next block →
recent activity
Analyzing
Block #101,986,020
12 transactions · 11 stateful · 2026-09-04 19:41:01 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,986,020
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execOrders
· blocks 1
#4
0xab083028
#5
0x59558d29
#6
setData
#7
withdraw
#8
0x57368ddf
#9
transfer
#10
execOrders
· blocks 1
#3
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0x91a74d74…548c
0x34b655…2a6f
4 touches
1 conflict
0x9d7ac3b9…22f8
0x34b655…2a6f
4 touches
1 conflict
0xb041f2a8…a44a
0x34b655…2a6f
4 touches
1 conflict
0xc52785b9…08f8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdac8e13c…bc65
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
0x34b655…2a6f
4 touches
1 conflict
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:
Perpl
1 conflict on slot
0xfd713bab1a…98a651
Audit this contract →
← previous block
·
next block →
recent activity