pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,627,599
← previous block
next block →
recent activity
Analyzing
Block #74,627,599
10 transactions · 8 stateful · 2026-05-14 22:41:23 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,627,599
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
#6
0xed82b078
#7
0x6a06500b
#8
setData
#9
0x39435dac
#2
flash
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
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x38b5b2ce…c5bb
0xfa32f9…f3f0
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x5a7fe7ea…c5b6
0x0555e3…2b9c
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
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
0x99f666e3cf…76b2a2
Audit this contract →
← previous block
·
next block →
recent activity