pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,743,938
← previous block
next block →
recent activity
Analyzing
Block #71,743,938
12 transactions · 9 stateful · 2026-05-01 14:10:59 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,743,938
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updatePrices
#4
0xeffdedb0
#5
0x69f4b4eb
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x3f5c179b
#9
0x0f6795d9
#10
0x0f6795d9
#11
0x39435dac
#2
updatePrices
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
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x35e52284…9269
0x065c9d…c394
2 touches
0 conflicts
0x3ffd5ba2…8225
0x065c9d…c394
2 touches
0 conflicts
0x487594a4…6c46
0x065c9d…c394
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:
0x7e9d3a8a…4f9fda
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity