pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,915,301
← previous block
next block →
recent activity
Analyzing
Block #94,915,301
8 transactions · 8 stateful · 2026-08-11 00:12:58 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,915,301
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x59558d29
· blocks 1
#7
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00a19519…11c6
0x34b655…2a6f
2 touches
0 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x4dc18bef…59d6
0x34b655…2a6f
2 touches
0 conflicts
0x4fb83d92…7e40
0x34b655…2a6f
2 touches
0 conflicts
0x51c64da3…3b8c
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity