pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,790,007
← previous block
next block →
recent activity
Analyzing
Block #73,790,007
12 transactions · 10 stateful · 2026-05-11 01:35:55 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,790,007
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbc3ec4c2
#2
execute
#3
0x39435dac
#4
0x121eab2f
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x6a0132f2
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…000d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x6e5e95e9…3a3b
0x1b6862…e19c
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
0x6713b0185b…1305f3
Audit this contract →
← previous block
·
next block →
recent activity