pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,529,625
← previous block
next block →
recent activity
Analyzing
Block #76,529,625
10 transactions · 7 stateful · 2026-05-23 18:17:05 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,529,625
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
removeLiquidity
#3
0x6df9e92b
#4
updateDataFeedsValuesPartial
#5
0x98717539
· blocks 1
#7
0x0f6795d9
#8
setData
#9
0x42dd8743
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07e31d21…af20
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x44ad89ba…cf83
0x23c26b…7777
2 touches
0 conflicts
0x81a7ba4d…8c4b
0x23c26b…7777
2 touches
0 conflicts
0x08fdca0b…4abf
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x3b9652cb…774a
0x5afd3e…7620
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
0x07e31d210d…64af20
Audit this contract →
← previous block
·
next block →
recent activity