pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,041,808
← previous block
next block →
recent activity
Analyzing
Block #71,041,808
5 transactions · 3 stateful · 2026-04-28 08:11:08 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,041,808
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
· blocks 1
#2
updateDataFeedsValuesPartial
#4
setData
#3
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x52a508f1…2e8a
0x1efe02…37d6
2 touches
0 conflicts
0x90ecce76…8a38
0x1efe02…37d6
2 touches
0 conflicts
0xbf63c90e…e855
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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:
0xfd44b351…7f00d1
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity