pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,285,898
← previous block
next block →
recent activity
Analyzing
Block #72,285,898
7 transactions · 6 stateful · 2026-05-04 02:26:28 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,285,898
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3d546218
#3
0x3f5c179b
#4
setData
#5
0x39435dac
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75f928fc…0465
0x34b655…2a6f
4 touches
1 conflict
0x77b7b407…ea83
0x34b655…2a6f
4 touches
1 conflict
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0xc166a323…1f33
0x34b655…2a6f
4 touches
1 conflict
0xd1ece6df…3b88
0x34b655…2a6f
4 touches
1 conflict
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
0x75f928fcad…c20465
Audit this contract →
← previous block
·
next block →
recent activity