pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,234,897
← previous block
next block →
recent activity
Analyzing
Block #76,234,897
11 transactions · 8 stateful · 2026-05-22 09:34:59 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,234,897
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
#5
executeBatch
#6
0xc5a04723
#7
forward
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#2
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x21dc9005…a06d
0x34b655…2a6f
2 touches
0 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
2 touches
0 conflicts
0x45e56656…0e33
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0xf9b8ae99dc…3532b3
Audit this contract →
← previous block
·
next block →
recent activity