pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,229,886
← previous block
next block →
recent activity
Analyzing
Block #76,229,886
12 transactions · 10 stateful · 2026-05-22 09:01:33 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,229,886
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x39ecce49
· blocks 1
#4
updatePrices
#5
addLiquidity
#6
redeemDelegations
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#10
setData
#11
0x670c21…fae3
#2
0x0c7abd22
#9
0xaf47a8bb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0xcb25539d…835d
0x9f3832…4ae4
4 touches
1 conflict
0xee67ecab…adca
0x9f3832…4ae4
4 touches
1 conflict
0x88c35155…6a0b
0xe1c8b7…3022
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
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:
0xe1c8b733…e33022
1 conflict on slot
0xa164d95170…fa1534
Audit this contract →
← previous block
·
next block →
recent activity