pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,077,742
← previous block
next block →
recent activity
Analyzing
Block #99,077,742
12 transactions · 12 stateful · 2026-08-25 15:24:07 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,077,742
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exec
#2
0x5acec890
#3
execOrders
· blocks 1
#4
0x59558d29
· blocks 1
#6
0xbb1740dd
#7
0x3f5c179b
#8
executeBatch
#10
0x6a8db40f
#11
setData
#5
0x59558d29
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0001
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0003
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0012
0x116e7d…d8f1
2 touches
0 conflicts
0xab2f6eed…254a
0x188d58…ea8e
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…00004b
Audit this contract →
← previous block
·
next block →
recent activity