pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,683,794
← previous block
next block →
recent activity
Analyzing
Block #71,683,794
10 transactions · 7 stateful · 2026-05-01 07:30:27 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,683,794
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeffdedb0
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x3f5c179b
#6
0x6df9e92b
· blocks 1
#8
0x2a34b5…8138
#9
0x4e8900…f91d
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
2 touches
0 conflicts
0x1c913164…5c2e
0x34b655…2a6f
2 touches
0 conflicts
0x23951077…539b
0x34b655…2a6f
2 touches
0 conflicts
0x313f2565…5b00
0x34b655…2a6f
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:
0x3bd359c1…15433a
1 conflict on slot
0x536e2740da…e461ac
Audit this contract →
← previous block
·
next block →
recent activity