pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,570,255
← previous block
next block →
recent activity
Analyzing
Block #76,570,255
8 transactions · 6 stateful · 2026-05-23 22:47:49 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,570,255
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6df9e92b
#2
0xab083028
#3
0x98717539
· blocks 1
#5
0x5f294c…256b
#6
0x734def…0b99
#7
setData
#4
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x10d80fee…dbda
0x1d1325…2305
2 touches
0 conflicts
0x3484c9df…bfd5
0x1d1325…2305
2 touches
0 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
2 touches
0 conflicts
0xdb067026…9eb8
0x1d1325…2305
2 touches
0 conflicts
0xea7ebe9d…709e
0x1d1325…2305
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
0xbfca3cd067…cd5023
Audit this contract →
← previous block
·
next block →
recent activity