pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,438,405
← previous block
next block →
recent activity
Analyzing
Block #76,438,405
12 transactions · 8 stateful · 2026-05-23 08:09:50 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,438,405
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
0x5339c59f
#4
0x000000b2
#5
updateDataFeedsValuesPartial
#6
0x100000b2
#7
0x0f6795d9
#8
0x0f6795d9
#9
0xbe70473d
#10
setData
#11
0x39435dac
#3
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bc3e255…0a0b
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x1e240e…10d4
2 touches
0 conflicts
0x00000000…0007
0x1e240e…10d4
2 touches
0 conflicts
0x00000000…0009
0x1e240e…10d4
2 touches
0 conflicts
0x00000000…f44c
0x1e240e…10d4
2 touches
0 conflicts
0x89969e43…c0ec
0x1e240e…10d4
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:
0xa6afd386…b0d132
1 conflict on slot
0x8bc3e2552c…6c0a0b
Audit this contract →
← previous block
·
next block →
recent activity