pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,198,994
← previous block
next block →
recent activity
Analyzing
Block #76,198,994
11 transactions · 10 stateful · 2026-05-22 05:35:33 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
#76,198,994
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x62be7533
#4
0x45761772
· blocks 1
#6
executeBatch
#8
createModule
#9
setData
#10
execOrders
#5
0x45761772
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000d
0x46a15b…4364
4 touches
1 conflict
0x405787fa…ee8c
0x46a15b…4364
4 touches
1 conflict
0x405787fa…ee8d
0x46a15b…4364
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13c19447…dc04
0x065c9d…c394
4 touches
1 conflict
0x0ac3f282…e0a7
0x065c9d…c394
3 touches
1 conflict
0xa2b6e782…911b
0x46a15b…4364
3 touches
1 conflict
0x746bf8fd…b5fe
0x065c9d…c394
3 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:
0x46a15b0b…7f4364
1 conflict on slot
0x0000000000…00000d
Audit this contract →
← previous block
·
next block →
recent activity