pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,421,891
← previous block
next block →
recent activity
Analyzing
Block #71,421,891
8 transactions · 8 stateful · 2026-04-30 02:22:41 UTC
Parallelism
63
/100
Blocked
38
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,421,891
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#6
setData
#4
0x3f5c179b
· blocks 1
#7
0x39435dac
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w2
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886f7fe6…8b7a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd01244ab…a05b
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
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:
0x34b6552d…112a6f
1 conflict on slot
0x886f7fe654…c88b7a
Audit this contract →
← previous block
·
next block →
recent activity