pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,923,387
← previous block
next block →
recent activity
Analyzing
Block #74,923,387
9 transactions · 6 stateful · 2026-05-16 07:35:29 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,923,387
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
· blocks 1
#2
0x5bf9264c
#3
0x5bf9264c
#4
withdraw
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#5
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xd5826a5f…05fd
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0001
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0002
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x1b1ee53c…5d8c
0x059114…ac3b
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x765c236f2d…b5ff45
Audit this contract →
← previous block
·
next block →
recent activity