pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,577,162
← previous block
next block →
recent activity
Analyzing
Block #76,577,162
10 transactions · 8 stateful · 2026-05-23 23:33:44 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,577,162
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x98717539
· blocks 1
#3
0x98717539
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x6a1239cf
#8
0x7150b6…980c
#9
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f5f775…010b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7ef40865…e995
0x065c9d…c394
2 touches
0 conflicts
0x941c21a6…c7fe
0x065c9d…c394
2 touches
0 conflicts
0xcb1a1042…161b
0x065c9d…c394
2 touches
0 conflicts
0xe8c4222f…c513
0x065c9d…c394
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:
Perpl
1 conflict on slot
0xb5f5f77567…50010b
Audit this contract →
← previous block
·
next block →
recent activity