pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,197,351
← previous block
next block →
recent activity
Analyzing
Block #76,197,351
11 transactions · 9 stateful · 2026-05-22 05:24:39 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,197,351
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
· blocks 1
#2
0x98717539
#3
executeBatch
#5
updateTemporalNumericValuesV1
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#4
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1f478980…5fca
0x1efe02…37d6
2 touches
0 conflicts
0x9560013d…8caf
0x91b81b…6d56
2 touches
0 conflicts
0xdd0b57a2…441f
0x91b81b…6d56
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0x787f8beb…56a3
0xaa3145…feec
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:
0x91b81bfb…8e6d56
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity