pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,555,612
← previous block
next block →
recent activity
Analyzing
Block #71,555,612
10 transactions · 7 stateful · 2026-04-30 17:17:16 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,555,612
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x1094dc9f
#4
0x5bf9264c
#5
updateDataFeedsValuesPartial
#6
0x5bf9264c
#7
0xeffdedb0
#8
setData
#2
0x0c7abd22
· blocks 1
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xc6a8c250…737b
0x1b6862…e19c
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x3b46a503…976b
0xd32edf…ff58
3 touches
1 conflict
0x2fdcb800…f674
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity