pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,295,448
← previous block
next block →
recent activity
Analyzing
Block #95,295,448
11 transactions · 10 stateful · 2026-08-12 08:15:03 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,295,448
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd60faa87
· blocks 1
#2
execOrders
#4
execFwdPositionOps
#5
executeBatch
#6
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
· blocks 1
#10
0xb8024e1a
#3
0x000000b2
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1632c2f…d991
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x850662…52d0
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x850662…52d0
4 touches
1 conflict
0x63f5c02f…6853
0x3bd359…433a
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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
0xb1632c2f29…54d991
Audit this contract →
← previous block
·
next block →
recent activity