pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,211,428
← previous block
next block →
recent activity
Analyzing
Block #73,211,428
12 transactions · 11 stateful · 2026-05-08 09:11:22 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,211,428
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#5
setData
#6
0x0c7abd22
· blocks 2
#9
forward
#10
0xeffdedb0
#7
0x0c7abd22
#8
0x62be7533
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
8
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdd8a6fb6…69cf
0xa6afd3…d132
3 touches
1 conflict
0x76b9f072…863c
0xd32edf…ff58
3 touches
1 conflict
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xa4e3b3b1bb…130911
Audit this contract →
← previous block
·
next block →
recent activity