pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,877,009
← previous block
next block →
recent activity
Analyzing
Block #100,877,009
12 transactions · 10 stateful · 2026-08-31 22:37:33 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,877,009
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
0x5acec890
· blocks 1
#4
0x59558d29
#5
setData
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#9
transfer
#10
0x6a9602a4
#11
0xc7068c7b
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5af10b50…8d5c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdb869c9d…407d
0x34b655…2a6f
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x16e51074…d6a7
0x34b655…2a6f
2 touches
0 conflicts
0x2407fe27…d2f5
0x34b655…2a6f
2 touches
0 conflicts
0x2cc76c10…81a5
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x5af10b50aa…348d5c
Audit this contract →
← previous block
·
next block →
recent activity