pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,449,663
← previous block
next block →
recent activity
Analyzing
Block #71,449,663
11 transactions · 10 stateful · 2026-04-30 05:27:45 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,449,663
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb3dd4ec4
· blocks 1
#2
poke
#3
poke
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#7
0x0c7abd22
#8
closeTrade
#9
setData
#10
0x39435dac
#6
0xb0435a94
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7957392…8e93
0x73ada1…8be0
4 touches
1 conflict
0x1b4df54f…7afb
0x754704…b603
4 touches
1 conflict
0xa3dc6f35…13e9
0x754704…b603
4 touches
1 conflict
0x8956cb26…42fa
0x73ada1…8be0
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…0004
0x43a05b…a68f
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:
0x73ada1ea…808be0
1 conflict on slot
0xb7957392e7…0d8e93
Audit this contract →
← previous block
·
next block →
recent activity