pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,974,402
← previous block
next block →
recent activity
Analyzing
Block #101,974,402
7 transactions · 6 stateful · 2026-09-04 18:42:04 UTC
Parallelism
57
/100
Blocked
50
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,974,402
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#3
0x59558d29
#4
setData
#2
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80342775…05c4
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0x165dc7e9…f4b1
0x34b655…2a6f
2 touches
0 conflicts
0x4534366a…8508
0x34b655…2a6f
2 touches
0 conflicts
0x4622b253…525e
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
0x8034277555…0d05c4
Audit this contract →
← previous block
·
next block →
recent activity