pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,243,931
← previous block
next block →
recent activity
Analyzing
Block #71,243,931
8 transactions · 7 stateful · 2026-04-29 06:36:49 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,243,931
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactOutputSingle
· blocks 1
#3
0x6463ffd1
#4
0x0c7abd22
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x36326531
#2
0xce1e7030
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
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 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
0x4245e4e8…096e
0x000000…012a
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:
0x00000000…a9012a
1 conflict on slot
0x18aed20c69…4f48f3
Audit this contract →
← previous block
·
next block →
recent activity