pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,413,921
← previous block
next block →
recent activity
Analyzing
Block #76,413,921
9 transactions · 7 stateful · 2026-05-23 05:26:58 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,413,921
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x5bf9264c
· blocks 1
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x91d7a6…aa22
#8
setData
#3
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24781048…4772
0x2a68ba…90c5
2 touches
0 conflicts
0x76e96198…eec4
0x2a68ba…90c5
2 touches
0 conflicts
0x23c90dba…2fb2
0x34b655…2a6f
2 touches
0 conflicts
0x3f39f77f…123e
0x34b655…2a6f
2 touches
0 conflicts
0x3f53c9f1…de17
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:
Perpl
1 conflict on slot
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity