pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,620,501
← previous block
next block →
recent activity
Analyzing
Block #100,620,501
9 transactions · 5 stateful · 2026-08-31 01:06:49 UTC
Parallelism
67
/100
Blocked
40
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,620,501
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
execute
#3
execOrders
· blocks 1
#5
0xed82b078
#7
setData
#8
0x61d59c2d
#4
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24bb46f7…3853
0x34b655…2a6f
4 touches
1 conflict
0x1aa4c755…8819
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2a76d80…ee44
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xdbb2fff3…b121
0x34b655…2a6f
4 touches
1 conflict
0xdbb2fff3…b122
0x34b655…2a6f
4 touches
1 conflict
0xf38f1915…a121
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
0x24bb46f739…c13853
Audit this contract →
← previous block
·
next block →
recent activity