pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,135,651
← previous block
next block →
recent activity
Analyzing
Block #96,135,651
12 transactions · 12 stateful · 2026-08-15 06:47:06 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,135,651
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x325dd70c
#2
execute302
· blocks 1
#4
commitVerification
#5
commitVerification
#6
execute
#7
execute
#8
execute
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
setData
#3
execute302
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0x317fc387…8bf2
0x0a3323…0a3c
2 touches
0 conflicts
0x25185a4e…ddee
0x34b655…2a6f
2 touches
0 conflicts
0x26d1b453…ce2c
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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:
0x0a332311…6e0a3c
1 conflict on slot
0x52c63247e1…bace02
Audit this contract →
← previous block
·
next block →
recent activity